Database Users

An actual successful unbrick?

I AM IN NO WAY SAYING THIS ACTUALLY WORKS!
THIS THREAD WAS CREATED TO PROVE THIS EITHER TRUE OR FALSE!
I personally have never bricked a phone, so didn't do this and cannot really confirm it, but reading over the thread it seems like it has worked for numerous people. The only problem with this is I would have imagined it would have blew up and everyone would know. If this does work, I wanted to share it. I understand how much a bricked device can get under one's skin. Anyways, it's also an older thread. (From 14th October 2009) Found it playing around in Sapphire Android Development but here's the thread:
http://forum.xda-developers.com/showthread.php?t=571457
Any thoughts on this? Some people say it worked, so people say it didn't. One guy said keep pulling cord out then plugging in and it will eventually catch it and install. I want to try and get this more out in the open and see if it actually does work, or if it doesn't.
I'm not trying to post spam, or raise hopes and just crush them. If this works, though, I want EVERYONE to know about this, if it doesn't - it was worth a try.
EDIT: I forgot to put this - I also want to know what an actual brick is. Is it actually where the phone won't turn on at all? If so - this isn't for a brick. However, the most common way I hear "brick" referred to as is "phone won't get into recovery, bootloader, or boot." If a brick is where your phone won't turn on - this is not for you. Once again, though, if you can get to splash screen this may be able to save you!

I've tried this method for a while with no provail, atleast on windows 7. It seems that some people can get their devices reconised by their operating systems while others cant, if this is the case then possibly fastboot can reflash it. Mine charges the device but does not identiy it at all.

Vibrant USB Connection Issue

Hello XDA Community!
I made a post about this issue before, but have more details so hopefully someone can help me figure out this issue.
My phone even when unplugged from my PC continuously says USB Connected/ USB Debugging in the notification menu.
Also, when I try and reboot the phone, instead of booting even to the Vibrant logo screen, the loading circle continuously blinks on and off, without actually booting.
As I type this, I am not holding down the power button, and the loading circle is blinking on and off by itself....
I used to be able to turn the phone on into recovery mode in the past, but now when I try to reboot into recovery I get a big yellow picture that says "Downloading"
The only way the phone will turn on is if it is plugged in.
I am fairly certain that this reboot issue and the USB issue are correlated in some way.
Did anyone else have this issue with their phones? And if so, how did you solve it?

Another thing I have just discovered...
When the phone is on and idle, the USB Connection notification will constantly blink on and off, which is why I think the phone would do the same when trying to power on!
Is this a hardware issue or a software issue?
I have not flashed anything in a very long time before this issue started happening so I believe a restore is unnecessary .
Someone please help me! This is very annoying, not only do I have NO notification bar because of the constant USB Connection notification turning on and off, I cannot turn on my phone at all unless it is plugged in!
ACK!

Take it back
I carry the insurance, so personally if this was happening to me I would not even mess with it. It sounds like you have a genuine problem with the phone and it needs to be replaced.
If it is possible to do try a nandroid backup of your phone to make getting back to where you are on your new device easier. Then take your phone back to stock with the recovery image here -->
http://forum.xda-developers.com/showthread.php?t=734475 (Thank you justanothercrowd)
One you have a stock device see if you are still having the issue. If you are take it back as defective. Even if you don't have the insurance, that sounds like a factory defect and should be covered by the factory warranty. The insurance just makes the process easier and makes sure they just give you a swap out at the store rather than having to wait for repairs. It also covers things the warranty does not, such as screen breakage - which is the specific reason I carry the insurance.

Ah crap wish I had insurance.... Do I have to do that whole odin procedure or is there a one click un root procedure as well?
Sent from my SGH-T959 using XDA App

Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App

I actually have not had reason to go back to stock, or even use odin yet at this point. My only roms were .zip files that I flashed via clockwork recovery.
I would say that your best best it to just follow the instructions on justanothercrowd's thread very carefully and deliberately. You are already having issues with reboots and your USB port, so this is not the time to deviate into experiments.
So to cut you off and just answer you next three questions:
Q) Can I just . . .
A) No! Just follow the directions exactly.
Q) But can I . . .
A) No! Just follow the directions exactly.
Q) Do I have to . . .
A) Hey look, Just follow the damn directions exactly!
Sorry, I can't help much beyond that. You chose to modify your phone and risk that you would not have issues, just like the rest of us here. In your case you did have issues. Now you have to get it back to stock so they don't have any reason to claim you caused this or that your warranty is void. I hope all goes well and it works out for you. Let as know and keep us posted. Good luck.

Lo N Slo said:
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
We must have been typing at the same time LOL.
There is a thread on unrooting, and basically it is just deleting a few things. After doing this you should not have any non-stock applications on the phone and there would be no reason to think it was rooted unless they went digging on the file system. Personally, I would delete those telltale files just in case, it looks a little suspicious to bring in a phone that looks like it has not been used since you bought it, but they have no proof you did anything and you can claim that you first did a factory reset to see if it would fix the problem.

Just want to keep this thread going, as I am having the exact same issue as the OP as of today. It happened out of the blue, and I haven't flashed anything new to my phone since JI6 was released, other than that, it's just a stock, rooted phone.
Hoping someone has an idea, but I will likely get it replaced under warranty, since the GPS has never worked either.

damnit damnit damnit I really wish I had warranty.
Random question about clockword mod recoveries.
If I were to do a backup right now, and save that file to my computer, could I restore that file later on a different phone after I root my replacement?
I don't have that many mods flashed, and I know all of the apps can be synced, but still it would be sooo convenient .

I believe that is how it works, so yes. It should be no different then when you clone a hard drive to put the image on multiple computers for easy distribution.
It is (just like the cloning metaphor) hardware specific. Just like I could not purchase a upgrade computer and expect a cloned image to work, don't expect to create a Vibrant backup and restore it on a Captivate.
That said, you should be able to restore your backup to new (identical) hardware.
By the way, what is the warranty on these? I thought it was a year for defects. I didn't think the Vibrant had been around long enough yet for anyone to be off warranty.

it should be a year, but there was also the option for a purchased warranty. I did not purchase a warranty, so I should be good on just my manufacturer's defect warranty

Being discussed here:
http://forum.xda-developers.com/showthread.php?t=817643

Real TRUE Brick this time

[PROBLEM SOLVED]
Ive been flashing back and forth to different builds trying which is better. I made sure I took the cautions not to flash builds that would brick my phone. There were 4 times that I soft bricked my phone but I was able to revive it. However, my little game has come to an end with this last one. The fault was this guide: http://forum.xda-developers.com/showthread.php?t=817186.
Little did I know, by doing a repartition and not loading anything to the NAND resulted in the bootloader not being installed. (Devices like this should have a ROM programmed to recover from these errors, think Gigabyte) Upon reset, the phone went out and didn't turn back on. ODIN reports success. Now the phone cannot turn back on, no matter what battery pull method I use, I get nothing on the screen. So much for fail-safe protocols Samsung has implemented, if there are even any. Poorly engineered!
EDIT:Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
EDIT 2: I am wrong about the bootloader being hardware. Some say it is flashable, so it is possible you can get a real TRUE brick and must need JTAG to revive it. Fortunately for me, I was able to use the USB JIG method to get it back up and running. Too bad, a new phone would've been nice.

Not poorly engineered, just poorly made user input.

Yes true, but samsung should have taken into account accidents like this will happen then they dont have control over who administers their update. People have bricked their phones by doing the factory update. When I design systems like these, I always make sure there is a fail safe backup that the user cannot modify. I am sure samsung has one and maybe they just dont let us access it.

I sometimes encounter the same error message but I never repartition. Luckily, i never clicked on it in Odin.

But you have to realize that most of those bricks are because people modified their phones from factory (ie. Voodoo and OCLF). Odin, a program used by internal Samsung engineers, was never meant for the public and shouldn't be used unless you know how to use it.
I agree, there should be an absolute fail safe if worse comes to worse, but the point I am making here is Samsung isn't wrong in this case.

When you violate warranties and experiment you tacitly accept responsibility for your actions. To not do so is not an act of rebellious ire...it is an act of denial.
Manufacturers do not, nor can not prepare for all scenarios because the possible number of scenario's to cover are legion. I don't see it as realistic especially for them to prepare for brick scenario's created by using a leaked internal engineering tool that the community has figured out largely through trial and error either. OTA and Mini Kies bricks they are responsible for, for obvious reasons, and Samsung and T-Mobile have taken responsibility for these scenarios because they are ones of their making.
XDA is not a place where people file warranty complaints (though some do complain). It is a place where people experiment, hack, and customize smartphones. Though some manufacturers do a better job than others at getting out of our way here (Samsung hasn't done so bad here relative to say Motorola), I don't think any of them particularly "care" about such community efforts in any meaningful sense. And why should they?
By modifying our devices aren't we quite clearly saying we're taking matters into our own hands? You have to balance your strong desire to tinker with the reality of where responsibilities lie.
These phones are some of the most difficult Android phones to brick. Anecdotally and statistically shown to be. Not impossible of course, but quite difficult. I feel for your bad experience but at least consider shouldering some of the blame.

Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?

I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?

Have you tried the jig method of getting into dl mode?

engineer14 said:
Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?
Click to expand...
Click to collapse
Keep on flashing, and eventually Odin will probably save your butt
Don't be scared of it, it works great. And it is safe to use.
========================================
I'm really sorry about your phone man, I didn't know that you had to NAND before re-partition, thank god I've never checked that but I might have in the future had you not shared this with us, so thanks a lot!
I guess your loss is everyone elses gain

No I havent tried the Jig method. The thread says that I need to have at least the samsung screen, so some kind of activity. This phone is just off, nothing comes on, no buttons, no screen...just dead. I think when I followed that guide, it told be to repartition and then reboot with the "PDA" field empty. So the phone rebooted when it finished formatting without installing anything. Now the NAND is at a "blank" state and I do not have any bootloader on there. Anyone know of a method to install a bootloader without the phone turning on?

I might be a little too far out of my element here but I think I found a guide to remove the sdcard and format it via pc one time when I was in a similar situation. I am at work currently and I also cannot remember if I have the link saved.

Maybe some phone expert in your city may help you to install the bootlaoder. I think it's called jtagging, I'm not sure though.
Sent from my SGH-T959 using XDA App

trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Just call Tmobile and tell then that you were upgrading to froyo 2.2 using Kies mini and it froze...

I had a black screen once. I was flashing in odin and knocked the cable loose. I think I had to remove the battery, open odin, plug the usb cable in, then install the battery and possibly hold a key down on the phone. I believe the download screen then came up. Otherwise the phone would not respond nor would any lights come on

trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.

masterotaku said:
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.
Click to expand...
Click to collapse
To disable driver signing, you ONLY need to run a single command and then reboot. And this applies to both Windows 7 and Vista.
Also to the OP.
You say you have no bootloader, but can't find ANYWHERE in this thread that says you were attempting to flash a bootloader. In fact, you can **** up partitioning, and your bootloader is still in tact. Been there, done that.
Do this. Plug the phone in, and leave it charging for about 30 minutes. Pull the phone off, hold the volume buttons, and plug the phone into a computer. See what happens. I had a ****ty situation end up happening to me, that I couldn't get the phone on for about 30 minutes. I had already even called T-Mobile for a replacement.

Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.

trdexalbee said:
Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
Click to expand...
Click to collapse
This "hardware" bootloader as you are calling it, is the exact bootloader that you can flash and TRULY brick your device. It is NOT a failsafe in the way in which you are referring. Please, please don't call it this. There are plenty of users on this forum that are clueless. The jig method, is a hardware jump point that Samsung has built in to allow you to get to download mode situations where the button method does not work.
As I mentioned earlier, you didn't flash a bootloader. Nor did you full on brick your device. Glad your device is back to normal now though.

my apologies then, it would be easier if samsung gave us the schematics, but that would never happen. So when we use odin to flash, we are not flashing the bootloader as well? Is the bootloader located on another ROM that is not easily accessible? I guess ROM would be the incorrect term since you stated you can "flash" the bootloader.

Galaxy Tab unbricking service

Stumbled upon this a bit ago, a company called Mobile Tech is offering an "unbricking" service on all versions of the Galaxy Tab. At the time of this writing they charge $50. I have not used this service, am not in any affiliated with this company and cannot vouch for their work, so beware. Just thought someone out there might use this when other options aren't available.
They have a nifty video up on youtube showing how they do it:

it will be a good help for those who brick their tab because they ain't follow the steps .. thanks for sharing this out

I can actually vouch third party for this service. Have had two friends use it and the device was returned within a few days. If I'm not mistaken, the guy lives in the southern US, but can arrange international he says.
Sent from my "better than an iPad" tab... Running Overcome GINGERBREAD!!!

This is cool, but I would recommend trying to go through Samsung first if you are still under warranty. I screwed up my primary bootloader and contacted them. They took care of shipping costs, fixed it up, and sent it back in about a week and a half. If Samsung hadn't fixed it I would defiantly have payed the $50 here though.

WOW, that seems like a lot of work for $50.
Thanks for the info, should I ever screw something up its nice to know there are people out there who can clean up my mess!

spacemoose1 said:
a company called Mobile Tech is offering an "unbricking" service on all versions of the Galaxy Tab.
Click to expand...
Click to collapse
Hi spacemoose1
Thanks for link and as always, thanks for honeycomb port. I would like to ascertain the definition of BRICK? with your help, if I may.
(disclaimer: pls forgive my wrong terms or exagerated explanation, but most importantly, pls correct me if I'm wrong)
BRICKed = software total lost, must use JTAG to force revive it, Samsung has it, or buy from web supplier around 300 USD ??? 500 USD ???
JTAG is a device to push software into all newly borned IC. I.E. when factory make IC, it's empty software inside, hence has a special device to push voltage into all sections of the IC, then force the code in.
Another term is ???CRASH??? or ???HANG???, (I don't know) anyway is not BRICKed, hence a reflash can recover it.
Samsung uses proprietary method a lot, not follow conventional, make usb driver very complex. USB driver install EXE around 15MB to 28MB depends on version, ALL work the same.
but, when the device = sgt7 in different state/condition, the driver must RE-ESTABLISH again, or else cannot work.
I.E.
state 1 = "OPERATIONAL"device in android operation, normal use, surf web, phone call etc
state 2 = "SLEEP" device powered off, show battery big icon charging when powered by charger
state 3 = RECOVERY mode
state 4 = DOWNLOAD mode - this is one of the way to FORCE flash to recover, as long as bootloader and something still intact
state 5 = PHONE-!-PC mode
stage 6 = "COMA" device powered off, NO show of battery big icon, even when charger supplied. Don't panic, let it charge fully 4 hours from 2 amperes supply, 10 hours from PC 500mA. It will start again !!!. Battery big icon will appear around 30% battery charged, I know because that's what I saw. I didn't check when it's in 10% or 20%. The 1st time I check was already 30% up from no-boot or no respone.
User need to plug device into PC during each of the state above at least once, in order for various flashing functions to work.
i.e. when it's a newly arrived device, usually install the usb driver 1st, with device state in android OS running properly, then plug in to USB and see "new device detected" installing, pls wait. Finished.
But when flashing via Odin using state 4 = DOWNLOAD mode, user may experience no connection, no COM3 or something. Because device must be unplugged in USB, power-up in state 4 = DOWNLOAD mode, plug in USB, "new device detected" installing = RE-ESTABLISH, done. UNPLUG USB, replug in usb, then COM3 appears FLASH will be succesfull.
same goes for other state.
p.s. many users reported BRICKed but then recovered WITHOUT JTAG is misleading beginners, hence should rename the term to ???CRASH??? or ???HANG???. although some previously use "SEMI-brick", which is acceptable.
stage 3 = ClockWorkMod flashing (super convenient, especially on the move without PC)
stage 4 = Odin / Heimdall both works (still convenient and easy )
stage 5 = Odin / Heimdall both works (still convenient and easy )
???CRASH??? or ???HANG??? or "SEMI-brick" is usually SUCCESFULLY recovered via restock+PIT
(final disclaimer, incase above is correct and help and is copied, pls correct whatever mistakes found, feel free.)
*** Thanks for all those who taught me my mistakes *** devs and fellow forumers

ManticoreX said:
This is cool, but I would recommend trying to go through Samsung first if you are still under warranty. I screwed up my primary bootloader and contacted them. They took care of shipping costs, fixed it up, and sent it back in about a week and a half. If Samsung hadn't fixed it I would defiantly have payed the $50 here though.
Click to expand...
Click to collapse
Yeah, warranty repair is always a better choice. But sometimes you've already voided the warranty, lol.

I guess, if u change factory installed rom/kernel warranty gonna be history
thanx for the post ... it might gonna be the last resort...

cx5 said:
Hi spacemoose1
Thanks for link and as always, thanks for honeycomb port. I would like to ascertain the definition of BRICK? with your help, if I may.
(disclaimer: pls forgive my wrong terms or exagerated explanation, but most importantly, pls correct me if I'm wrong)
BRICKed = software total lost, must use JTAG to force revive it, Samsung has it, or buy from web supplier around 300 USD ??? 500 USD ???
JTAG is a device to push software into all newly borned IC. I.E. when factory make IC, it's empty software inside, hence has a special device to push voltage into all sections of the IC, then force the code in.
Another term is ???CRASH??? or ???HANG???, (I don't know) anyway is not BRICKed, hence a reflash can recover it.
Samsung uses proprietary method a lot, not follow conventional, make usb driver very complex. USB driver install EXE around 15MB to 28MB depends on version, ALL work the same.
but, when the device = sgt7 in different state/condition, the driver must RE-ESTABLISH again, or else cannot work.
I.E.
state 1 = "OPERATIONAL"device in android operation, normal use, surf web, phone call etc
state 2 = "SLEEP" device powered off, show battery big icon charging when powered by charger
state 3 = RECOVERY mode
state 4 = DOWNLOAD mode - this is one of the way to FORCE flash to recover, as long as bootloader and something still intact
state 5 = PHONE-!-PC mode
stage 6 = "COMA" device powered off, NO show of battery big icon, even when charger supplied. Don't panic, let it charge fully 4 hours from 2 amperes supply, 10 hours from PC 500mA. It will start again !!!. Battery big icon will appear around 30% battery charged, I know because that's what I saw. I didn't check when it's in 10% or 20%. The 1st time I check was already 30% up from no-boot or no respone.
User need to plug device into PC during each of the state above at least once, in order for various flashing functions to work.
i.e. when it's a newly arrived device, usually install the usb driver 1st, with device state in android OS running properly, then plug in to USB and see "new device detected" installing, pls wait. Finished.
But when flashing via Odin using state 4 = DOWNLOAD mode, user may experience no connection, no COM3 or something. Because device must be unplugged in USB, power-up in state 4 = DOWNLOAD mode, plug in USB, "new device detected" installing = RE-ESTABLISH, done. UNPLUG USB, replug in usb, then COM3 appears FLASH will be succesfull.
same goes for other state.
p.s. many users reported BRICKed but then recovered WITHOUT JTAG is misleading beginners, hence should rename the term to ???CRASH??? or ???HANG???. although some previously use "SEMI-brick", which is acceptable.
stage 3 = ClockWorkMod flashing (super convenient, especially on the move without PC)
stage 4 = Odin / Heimdall both works (still convenient and easy )
stage 5 = Odin / Heimdall both works (still convenient and easy )
???CRASH??? or ???HANG??? or "SEMI-brick" is usually SUCCESFULLY recovered via restock+PIT
(final disclaimer, incase above is correct and help and is copied, pls correct whatever mistakes found, feel free.)
*** Thanks for all those who taught me my mistakes *** devs and fellow forumers
Click to expand...
Click to collapse
I pretty much agree, but I might refine:
BRICK= Unit does not power up, visibly charge, reach a boot-screen of any kind including a service or "download" screen. A device in this state requires service from the manufacturer or an individual equipped with the proper tools. There is no other way to recover a device in this state.
SOFT-BRICK= Unit powers up, reaches a "download" or service screen, visibly charges but does not boot into an OS. Crashing, hanging etc. all apply here. It is easy to recover a device from this state so long as one has access to a firmware that was designed for the device and the ability to flash said firmware.
SEMI-BRICK= See soft-brick above
JTAG= Provides access to system hardware by applying the correct voltage to the correct pins in order to push software via an external program.
In regards to the usb drivers, there are only actually 4 states
1. Active userspace
2. Serial gadget mode
3. Recovery
4. USB storage mode
And there is a separate driver for each of these (except recovery) in the Samsung driver package that should install automatically when the device is plugged in during normal use on a stock rom, or with the installation package available on the web.
The rest of it you've got pretty much correct.

Money seems right, but the amount of work that guy has to go thru is amazing, so much to tare it apart, and reassemble. Then again when it is put back toether, he checks it, what if it did not take the fix... all over again.

Hardbricked Tab Save by Mobile Tech
I hardbricked my galaxy tab bought in Cambodia. My little brother open the tab trying to take the battery off and put it back on, thus void the warranty, found him on the Samsung vibrant forum, sent the tab to him got it back good as new. This person is professional, honest and good communication with his customers, you'll be happy with his work, if he can't fix it you get your money back (minus shipping and diagnosis)...Glad he is arround to help...

spacemoose1 said:
I pretty much agree, but I might refine:
BRICK= Unit does not power up, visibly charge, reach a boot-screen of any kind including a service or "download" screen. A device in this state requires service from the manufacturer or an individual equipped with the proper tools. There is no other way to recover a device in this state.
SOFT-BRICK= Unit powers up, reaches a "download" or service screen, visibly charges but does not boot into an OS. Crashing, hanging etc. all apply here. It is easy to recover a device from this state so long as one has access to a firmware that was designed for the device and the ability to flash said firmware.
SEMI-BRICK= See soft-brick above
JTAG= Provides access to system hardware by applying the correct voltage to the correct pins in order to push software via an external program.
In regards to the usb drivers, there are only actually 4 states
1. Active userspace
2. Serial gadget mode
3. Recovery
4. USB storage mode
And there is a separate driver for each of these (except recovery) in the Samsung driver package that should install automatically when the device is plugged in during normal use on a stock rom, or with the installation package available on the web.
The rest of it you've got pretty much correct.
Click to expand...
Click to collapse
You should post this in Q/A thread on its own as its very helpful and maybe it will stop the 1% of people saying help my phone is bricked comments ... the other 99% don't read anyway otherwise they would discover their phone isn't bricked and if they read properly it would not have gotten to the state in the first place .. and no I never posted something like that myself >:¬}
but well done on this..

alexgogan said:
You should post this in Q/A thread on its own as its very helpful and maybe it will stop the 1% of people saying help my phone is bricked comments ... the other 99% don't read anyway otherwise they would discover their phone isn't bricked and if they read properly it would not have gotten to the state in the first place .. and no I never posted something like that myself >:¬}
but well done on this..
Click to expand...
Click to collapse
+1
Sent from my GT-P1000 using Tapatalk

Nice find. For that amount of effort disassembling, and reviving, $50 is a very realistic price. I'll keep these guys in mind if I run into issues with my tab.

$50 for that much work is an absolute bargain! I wish I didn't live in a country where you get charged $200/hr for someone to pick their nose.

It's actually not that much more difficult than popping an OS install CD into a hosed computer and pressing 3 keys to let it run through the installation after flashing a corrupt motherboard BIOS. Yes, it takes familiarity with the software and hardware, but it's by no means a feat that requires a special skillset.
Granted, few people have JTAG stuff handy, so $50 is definitely worth it if you've hosed your device, but don't make it sound like he's sweating and coding the bootloader by hand, strenuously manipulating micro tools to disassemble the tablet and flipping DIP switches to restore the bootloader. You spend 5 minutes taking apart the tablet, you attach the JTAG cable, run the supplied software on your computer, and sit there recording the screen with your video recorder while the progressbar moves from 0 to 100.
Again, it's worth $50 simply because not everyone and their mother has JTAG hardware sitting around, but by no means is it hard. It's the same reason I can get away with charging $100 to clean viruses off of a computer. People either don't have the tools or don't know how to use them. That being said, I don't know a damn thing about using JTAG to restore a corrupt bootloader, nor do I have the right hardware, so I'd pay $50 if I were ever in the situation.
Edit: And yes, $100 for a virus clean is a lot, but people generally change their mind when I explain to them why they got viruses, as well as installing proper antivirus software and then instructing them on how to avoid infection in the future. I rarely get repeat business from the same customer but I get A LOT of referrals ;p They're happy paying that much when the person educates them instead of cleaning, not installing/explaining, then having to bring the computer in again two weeks later for another wallet-gouge, which most other computer 'repair people' gladly do over and over.

Everything in this world is rinse and repeat... The money comes from time spent learning to use the hardware properly, micro soldering skills (which isn't easy, no matter who you are), confidence enough to offer it as a service, not to mention the couple hundred bucks for the jtag software and hardware.
Now, the fact that if you have your device in a bricked state you likely voided the warranty, it's a 600 dollar brick if your samsung tech recognized it... 50 bucks is a steal to not deal with samsung anyway.
Try to be less pompous next time oh savoir of the hundred bone virus... Your poop stinks too, promise.
Sent from my "better than an iPad" tab running Overcome Hermes.

LycaonX said:
It's actually not that much more difficult than popping an OS install CD into a hosed computer and pressing 3 keys to let it run through the installation after flashing a corrupt motherboard BIOS. Yes, it takes familiarity with the software and hardware, but it's by no means a feat that requires a special skillset.
Granted, few people have JTAG stuff handy, so $50 is definitely worth it if you've hosed your device, but don't make it sound like he's sweating and coding the bootloader by hand, strenuously manipulating micro tools to disassemble the tablet and flipping DIP switches to restore the bootloader. You spend 5 minutes taking apart the tablet, you attach the JTAG cable, run the supplied software on your computer, and sit there recording the screen with your video recorder while the progressbar moves from 0 to 100.
Again, it's worth $50 simply because not everyone and their mother has JTAG hardware sitting around, but by no means is it hard. It's the same reason I can get away with charging $100 to clean viruses off of a computer. People either don't have the tools or don't know how to use them. That being said, I don't know a damn thing about using JTAG to restore a corrupt bootloader, nor do I have the right hardware, so I'd pay $50 if I were ever in the situation.
Edit: And yes, $100 for a virus clean is a lot, but people generally change their mind when I explain to them why they got viruses, as well as installing proper antivirus software and then instructing them on how to avoid infection in the future. I rarely get repeat business from the same customer but I get A LOT of referrals ;p They're happy paying that much when the person educates them instead of cleaning, not installing/explaining, then having to bring the computer in again two weeks later for another wallet-gouge, which most other computer 'repair people' gladly do over and over.
Click to expand...
Click to collapse
I've got to call you out on this one. Mis-connecting or shorting any wires will lead to a damaged PCB and an un-resurrectable TAB. I'm also a Systems Admin for a living so I understand where you are coming from. You must realize that I solder at levels of .1mm in spacing on the Captivate, Vibrant and Nexus S. Electrical engineers and technicians have first hand talked with me about the difficulty of doing this and is NOT something that anyone can do. You'd think twice when you burn up a phone or two valued at $500 a pop trying to JTAG them. There is more skill involved than you would think. Not to mention the liability when dis-assembling the device. JTAG software is decent but it's not fully automated. There are TCK frequencies, RTCK frequencies different PBL partition sizes, full dcc loader read/writes and the requirement of EXACT voltage from an external power supply that are needed in MANY cases. Plus, there is little to no support when fixing a device. This means that if you can't figure it out, nobody else is going to for you. I'm not trying to brag but yet point out that this isn't like plugging in your phone for an ODIN flash. I've taken hundreds of hours of time and 1000's of dollars to create what I feel is the most trusted JTAG authority online ANYWHERE. I greatly appreciate having the opportunity to help the community and enthusiasts in this community. If this was as easy as you are claiming, you could get JTAG hardware and a manual at Best Buy. I have to say you put it best when you said you don't know anything about JTAG... Ok end of rant I was just a bit bothered by your post.
Ok with that being said, thanks for the personal testimonies and compliments. I will be here whenever anyone needs JTAG assistance in the future or around the forums to help answer Q&A when it doesn't require JTAG. Here is a Nexus S promo to realize how tiny some of these things are
http://www.youtube.com/watch?v=Ecp8jKmm48k

i would love to learn more on how to do stuff like this if i had moneyz. the .1mm ext.
not just for android but to make my own ish.
thanks for the awsome videos.

Thanks for the link, hope I won't need it ;-)
Sent from my GT-P1000 using XDA App

My experience with tech support so far...

I really just need to vent about this...
I initially emailed on 05/09/2015, I've made it nowhere in the RMA process other than verbally assaulting their tech support (I only sort of feel bad). I've been moved around to five different people. The first three told me the exact same thing. The fourth did what the third said they would, and the fifth is what the fourth said they would be.
05/09/2015 Melissa wanted a video of the problem.
05/15/2015 I told her that's not something I should have to do for a well documented defect.
05/17/2015 Chris wanted a video of the problem.
05/17/2015 I told Chris I didn't have another device to record video with and again said I thought it was ridiculous I had to do this.
05/17/2015 Chris requested a screencast video of the device showing its ghost touches.
05/17/2015 I told Chris that it was a cool day so that the device was not acting abnormally at the moment and asked if I should warm it up in the oven.
05/17/2015 Chris thanked me for the reply and said we would pick up once the problem showed again. 05/17/2015
05/17/2015 I sent Chris a link to "lmgtfy" with the search query "one plus one touch screen issues". 86.8M results. I then told him if we waited for my device to show the defect again, that I could be in a life or death scenario and being unable to unlock my device is just... I'm dead. Worst case, but seriously you guys. It could happen. 05/17/2015
05/17/2015 Chris again thanked me for the reply and said he would be escalating it to the proper department for assistance. 05/17/2015
05/19/2015 Elmer wanted a video of the problem, and pictures of the device.
05/19/2015 I told Elmer I didn't have another device to take video or pictures with, and then suggested he do an Advance RMA so that I could take pictures with a properly function OPO.
05/19/2015 I was with a friend that day and I low and behold, the scenario where I couldn't unlock my phone showed up! So I sent it to them.
https://drive.google.com/file/d/0B4MvQwyeqEj2M1dQSWNMaFdNOGs/view?usp=sharing
05/20/2015 The next day I send another screencast video of my phone.
https://drive.google.com/file/d/0B4MvQwyeqEj2X3BlVW5tYURHZzA/view?usp=sharing
05/21/2015 I send them an email saying I like how quickly the replies were when I was fighting them on the videos, but then don't reply when I do. I also told them they had lost me permanently as a customer. "it's good to end bad relationships early."
05/22/2015 Chrystle sends me links to two different zip files. One called, ONEPLUS+ONE-FIX-Windows.zip, and the other OPO-Display-patch.zip. She informs me that they are Windows or Mac only.
05/22/2015 I send two different messages, one saying that I do not run Windows or Apple operating systems on my computer, requesting that I get something that will be flashed in recovery, or something that could work with Linux. Fast forward through my work shift. I get home and download the files anyway and extract them. there is a .bat file in there with a bunch of commands flashing partition files using fastboot. open up a terminal and I start copying and pasting the lines so I don't make any mistakes. Get to the one about flashing the userdata partition, and the script as a typo. the file has a capital G and the script is showing a lower case g. Those are 500MB "patches" just FYI. One did nothing, and the other made it worse. They were both CM11S. http://i.imgur.com/bEq9Boy.png http://i.imgur.com/InuCpLo.png respectively.
05/23/2015 I send several messages. It's early AM but I send an email asking if it's amateur hour because of the typo in the first rom. Then another message saying that the typo was also in the other patch zip. Yeah, that's right. both zips had the same typo'd batch script. It's funny they treat us like we know nothing. I finish the email with "Idiots."
05/24/2015 Cherie asks if my device was ever dropped, bumped(???), or exposed to liquids. Also goes on to explain that the CPU and Camera are close together and that the camera material transmits heat quickly so the device can feel warm there. Then suggests I close apps running in the background. Also then recommends that I recondition the battery by fully charging and discharging it three times. And also says not to use the phone while it's charging because it needs to rest. She then wanted me to install a multitouch testing app to screencast, and also requests pictures.
05/24/2015 I say I've never dropped the device, and am unsure what they mean by bumped. And say the device hasn't been anywhere near water in my possession. (near enough to cause an issue anyway). I'm just going to quote myself here, "What causes overheating of the display? And my typing is not the problem. HTC MyTouch 4G, Samsung Galaxy S3, LG Nexus 4. Those three devices could keep up with me. Ah, those were the days. Such fond memories of accurate touch screens.S o the CPU is close to the other components in the phone? That's amazing! How do you do it in such a small package? Crazyness. Though, my Nexus 4 is even smaller, must be magic to be able to fit the cpu and camera in there together. Material of the camera transmits heat... Well, most things are conducive of heat. I close background apps frequently enough. I keep the screen brightness close to 50%. The phone needs a rest while charging? Why is that? Did it get fatigued? Is it tired? Did it have a long day? I've never had an electronic device that "needs to rest". Sounds like YOU NEEDed to improve the cooling capabilities of the device. My battery usage is also not abnormal, nor under heavy load does the battery get hot. I get 7 hours of screen on time. That's absolutely amazing! Now if only I could use it for those 7 hours I'm able to turn the display on. Common problem with Li-Po batteries that are old. Are you saying I have an old battery in my device that needs to be reconditioned? I better not since I've only just bought the phone a month ago. Pull the notification drop down menu down, press the back button, and restart the device... What? How's that any different than just rebooting it? The last step of this RMA process pretty much sealed the deal that yall are idiots, and this is just kind of the icing."
05/25/2015 Cherie requests pictures of my device. And says if I do she promises my device will be like new once she forwards me to their Level 2 support.
05/25/2015 I send them the pictures they requested.
05/26/2015 I send them a screencast AGAIN saying, "Can we stop playing games?"
https://drive.google.com/open?id=0B4MvQwyeqEj2dGNidWNxRlkzVFE&authuser=0
05/26/2015 Llores sends me an email about setting up a remote session with Level 2 support. Requests that I download a few files and to set up an appointment. For Windows there were five zips linked. One for OxygenOS(I'm presuming) "oxygen-dlt.rar" 784MB. One for CyanogenMod(again, presuming) "DLT-CM.rar" 512MB. a Certificates rar that I did not download, as these are probably Windows driver things. The Android SDK which I did not need. CM11S from cyngn website 510MB. And an archive titled AFX. Which has two files in it, a persist.img and a reserv4.img... a measly 10KB.
05/26/2015 "Are you new? Or did you just not read anything? The operating system on my computer is Debian Linux. No one needs to remote access my computer because I've already proven I'm smarter than you. I do not trust any of you to access my personal computer. It is unnecessary. If you're level two tech support maybe you can fix the amateur hour typo in the previous fixes automated scripts that didn't do jack didn't squat for my device. My device has an intermittent hardware issue that needs to be resolved with a different device that has been factory reconditioned or refurbished. No amount of software is going to fix a hardware issue. Waaaaiiiittttt, you guys are that dumb huh? Holy ****. LOLOLOL." and shortly after, "I hope you can understand, that I do not want anyone accessing my computer, and running commands. A miskey from an idiot at OnePlus (witnessed from a script typo and the inability to read a conversation history) could erase all of my personal files. I would be highly aggravated, and you've only seen me mildly irritated."
And there we are so far. This kind of service is absolutely unacceptable. It doesn't matter how much the phone was. Someone on the OPO forums said they paid for the phone, not tech support and warranties.
Also, the DLT files are password protected, which I'm sure the L2 support lackey knows the passwords, I'm trying to break in to it using rarcrack, but.... bruteforcing something is relatively slow.
05/27/2015 Cherie emails me again and from the sounds of it, she had no recollection of our previous conversation. She says that Level 2 tech support needs to remotely access my computer.
05/27/2015 I tell Cherie that I've already mentioned I will not be allowing anyone from their company to remotely access my computer. Request one of their computers be sent to me for them to remotely access and flash my phone. Then go on to say that they probably won't do that because you don't trust me with your data as much as I don't trust them with mine. Tell them I will be going through with a paypal dispute.
05/27/2015 Cinderella says, "Thank you so much for the response. We understand your point of view on the said issue,I understand how frustrating it is of not being able to use your Oneplus phone and have to go through with this process. Many felt the same reaction too. In the long run, numerous Oneplus owners found out that patch fix resolved their touchscreen issues as it may install those missing "TPK firmware" on the phone."
05/27/2015 I say I don't understand why someone needs to remotely access my computer when I've already proven that I'm more than capable. And that if she gives me the password I'll be out of their hair, forever and ever.
05/27/2015 Cinderella says she understands that a remote access can be challenging but my ticket is being handled in a timely manner by tech support and that remote sessions are recorded for security purposes.
05/27/2015 I tell Cinderella that they've done nothing to gain the trust for me to open up my computer to them. Say if they give me the passwords to the .rar's I would set up a remote session.
05/28/2015 Ethan emails me informing me that it is the tech that will be unzipping the files during the remote session, and to let him know when I've booked an appointment.
05/28/2015 I get on the site to book a remote session. The next available time is 06/06/2015 @ 6:30pm. No idea if that's local time or not, But either way, who is at work at 6:30pm OR 9:30PM? I send Ethan an email telling him the company is a joke, and that I'm getting my money back. I tick the "this issue is resolved" and hit the reply button.
I am really sad though, I love the phone and I wish it would work properly.

they are only thiefs, no other adjective describe them.
They put a fail cheap ****ty display on this device, and after a random time (depend from many enviroments, temperature, isolating, what you eat... ) it appears the non responsive/ghost touch issue.
They don't want repair or change, and if you have only a micro dent on the frame... goodbye
the incredible, it's that they have prepared some zips with naming "fix touch" etc... they are ridiculous... This phone have a target of 90% middle/high geek, so, they don't want this bull**** no resolutive sw, but they want try and flash whatever they want, when they want, and they want that almost the device have a display working !!!
They stop say try what rom you prefer, your warranty will remain..... YES, RIGHT, because we haven't any WARRANTY on display !!!

This is exactly why I buy used, broken devices for dirt cheap and repair them myself. I got my 64gb 1+ off eBay for $115 after repairing it's screen.
Screw warranties, support, etc.

silverton said:
I really just need to vent about this...
I initially emailed on 05/09/2015, .....
Click to expand...
Click to collapse
I have similar experience and I too reach the point that tell them "NO way I gave you remote control"
They sad again, that second level technical will decide if my phone is for RMA.
I think with my refuses to gave them access they will close my case. I think it is not legal but.....
I just want to send phone and they fix or gave new one and I sale fast.
What we must do?
I bought phone in October, so obviously I can't claim refund from PayPal

It's been... 6 or 7 weeks now since I first submitted ticket. Somehow I managed to skip the remote session, went from asking me to book session, to setting up the phone getting picked up.
But...
A week after they said they received it, they come back saying water damage, apparently the the LDI in headphone jack was tripped and want me to pay for repair. I basically argued back, told them it had never been anywhere near and liquids.
Lo and behold, they come back saying they've made a mistake. On re checking, there is no water damage, and so now will replace my phone. Imagine I'd caved and paid for repair, or just had them send it back...
... Finding it hard to believe they made a genuine mistake...

mozyman said:
It's been... 6 or 7 weeks now since I first submitted ticket. Somehow I managed to skip the remote session, went from asking me to book session, to setting up the phone getting picked up.
But...
A week after they said they received it, they come back saying water damage, apparently the the LDI in headphone jack was tripped and want me to pay for repair. I basically argued back, told them it had never been anywhere near and liquids.
Lo and behold, they come back saying they've made a mistake. On re checking, there is no water damage, and so now will replace my phone. Imagine I'd caved and paid for repair, or just had them send it back...
... Finding it hard to believe they made a genuine mistake...
Click to expand...
Click to collapse
**updated with a sad ending**
You're not the only one I've read about having them try to claim that the liquid sticker was tripped, and then back track when they're called out on it.

Sounds much alike the issues I have with OnePlus support right now. My 2 has what I strongly suspect hardware issues. I can say that I'm pretty sure, that is after worked for a Swedish/Japanese mobile manufacturer for almost 16 years. So I know a bit about mobile phones . I think in the end the wankers will not give me another phone. Their tactics is to f**ck you around until you give up. It's a shame actually, I love their products but the company is rotten to the core how they conduct themselves. I think I'll write an email to Carl Pei in Swedish and tell him my two cents about this matter. I don't except it to do any good but perhaps I'll catch him of guard. If anybody is interested I'll let you know how that wen't down.