Repair facility for bricked Galaxy Tab s 10.1 (SM-T800) - Galaxy Tab S Q&A, Help & Troubleshooting

Hard bricked my tablet trying to uninstall TWRP. No combination of keystrokes will do anything. It is stuck with the display on showing "Running OpenRecoveryScript". I am assuming that it it will just have to run the battery down.....and that will be that. Looking for a reputable facility that would have capability of recovering this.
Thanks

XDA Visitor said:
Hard bricked my tablet trying to uninstall TWRP. No combination of keystrokes will do anything. It is stuck with the display on showing "Running OpenRecoveryScript". I am assuming that it it will just have to run the battery down.....and that will be that. Looking for a reputable facility that would have capability of recovering this.
Thanks
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
I don't know of any repair facilities, nor could I find any mention of them on your XDA device section, but you may be able to get into Download Mode with a Download Mode Jig. I'm just not sure if the complete loss of power will make a difference in the process of your recovery.
At any rate, I am connecting this thread to the forum your device experts can be found in:
> Samsung Galaxy Tab S > Galaxy Tab S Q&A, Help & Troubleshooting
Please note, in order to respond to replies, you will need to be registered for an XDA account.
Hope this helps, and good luck!

possible solution
XDA Visitor said:
Hard bricked my tablet trying to uninstall TWRP. No combination of keystrokes will do anything. It is stuck with the display on showing "Running OpenRecoveryScript". I am assuming that it it will just have to run the battery down.....and that will be that. Looking for a reputable facility that would have capability of recovering this.
Thanks
Click to expand...
Click to collapse
check samsung-firmware.org

Another option when it come to firmware as well:
> Samsung Galaxy Tab S > Galaxy Tab S General > [TOOL] SamFirm - Samsung firmware downloader & checker

XDA Visitor said:
Hard bricked my tablet trying to uninstall TWRP. No combination of keystrokes will do anything. It is stuck with the display on showing "Running OpenRecoveryScript". I am assuming that it it will just have to run the battery down.....and that will be that. Looking for a reputable facility that would have capability of recovering this.
Thanks
Click to expand...
Click to collapse
That's not hard bricked at all and easily recovered. I'm guessing you tried factory reset from within android which caused the issue.
You have probably solved this by now so will leave it there. If not post back.

Related

[Q] Unbrick SGH-T999 That shows up in device manager QHSUSB_DLOAD

anyone know if there is a way to unbrick a sgh-t999 that shows no power but when I plug it into my computer I get a device connected in the device manager with QHSUSB_DLOAD?
That means its hard bricked. Sorry.
Sent from my SGH-T999 using xda app-developers app
jackalsmp said:
anyone know if there is a way to unbrick a sgh-t999 that shows no power but when I plug it into my computer I get a device connected in the device manager with QHSUSB_DLOAD?
Click to expand...
Click to collapse
Yes its called JTAG
After owning SGS for 4 days, got this message already. Luckily i can cancel my contract or target will replace this with new one. Oh well that's the life of being an Android user
jtag
I think it is a hard brick also, even jtag can't save it. I got one of these and it will not boot even though boot loader is fixed. But it booted a few times before when I was jtagging where I accidentally crossed the jtag wires I don't know how the wires are crossed so I can't do it again. but it seems it can be boot from jtag if something is being connected correctly; however without the jtag being connected it will not boot at all. Nand and everything else seems fine. Feels like something is forcing it to go into ZESU Flash Device mode.
Hope for Bricked SGH-T999 and several variants
Found this too late to help me so I post it here to brighten this otherwise gloomy thread and give hope to others lead here by Google search.
You may be able to unbrick your T999 (and a few other variants) after all by booting your phone from a specially prepared SD card.
[HOWTO] UnBrick T-Mobile S III QHSUSB_DLOAD w/Video Walkthrough
Thread By: KAsp3rd
http://forum.xda-developers.com/showthread.php?t=2439367
Panamon said:
Found this too late to help me so I post it here to brighten this otherwise gloomy thread and give hope to others lead here by Google search.
You may be able to unbrick your T999 (and a few other variants) after all by booting your phone from a specially prepared SD card.
[HOWTO] UnBrick T-Mobile S III QHSUSB_DLOAD w/Video Walkthrough
Thread By: KAsp3rd
http://forum.xda-developers.com/showthread.php?t=2439367
Click to expand...
Click to collapse
What a Lifesaver! Thank you much.

[Q] bricked device

Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
HANSB57 said:
Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
Click to expand...
Click to collapse
Can you access recovery or download mode?
sefrcoko said:
Can you access recovery or download mode?
Click to expand...
Click to collapse
No I cant.
All combinations (power, volume home etc.. failed)
Removed back cover, disconencted battery
No result.
How did you remove the back cover?
I've been able to get mine out of pickles not involving the /boot partition by holding down the volume down, home and power keys simultaneously. Shortly after the model 5110 message displays, I release power and am asked if I really want to put the device into update mode.
I use Odin to write in the firmware I downloaded from samfirmware a few weeks ago.
I needed to do this last night after trying to disable a few system apps. I'm not sure which, probably a thing called "bubble," but as soon as I had, the device froze. A reboot went all the way through but then locked up after my startups finished.
I also needed to do this after something much closer to a soft brick involving trying to use the Xposed framework to change lcd density.
I reflashed and was able to defrost and I was back in business.
roustabout said:
How did you remove the back cover?
I removed it by gently prying the white back cover of.
I would recommend agains it because its delicate.
But I think you would advice me agains bricking my device. :angel:
I cant get it in download mode.
It wont show the charging again when charging.
It seems dead
Anybody might have a clue??
Click to expand...
Click to collapse
something just occurred to me - you've pulled out your sdcard and set it aside? sometimes a bodgy sdcard can get in the way of boot up, though it seems unlikely here.
It doesn't seem that patching the framework, even if it keeps you from booting past the model # screen, should be able to keep the device from at least powering on.
If you connect it to your PC and try holding in power for ~30 seconds, does any USB device or android device activity occur at all, even if a device appears and disappears again?
I did find that I had a "konawifi" device attached to my PC and needed to update its driver to access the device in CWR mode.
roustabout said:
something just occurred to me - you've pulled out your sdcard and set it aside? sometimes a bodgy sdcard can get in the way of boot up, though it seems unlikely here.
It doesn't seem that patching the framework, even if it keeps you from booting past the model # screen, should be able to keep the device from at least powering on.
If you connect it to your PC and try holding in power for ~30 seconds, does any USB device or android device activity occur at all, even if a device appears and disappears again?
I did find that I had a "konawifi" device attached to my PC and needed to update its driver to access the device in CWR mode.
Click to expand...
Click to collapse
I pulled the SD card
This afternoon I will try your tip (connecting it to the PC)
I also will try a jig although I think this is useless
My last resort is back to Samsung. I have 2 choices, repair or make a frisbee out of it. I prefer the first option especially beacause I was rather pleased with the device
I tried making a jig when I bricked my Galaxy Media Player, and it did not work. Samsung repaired it, eventually.
roustabout said:
I tried making a jig when I bricked my Galaxy Media Player, and it did not work. Samsung repaired it, eventually.
Click to expand...
Click to collapse
Just brought it back to shop. Will sent it back to Samsung.
will take 3 weeks. Luckely I have my trusted tab 10.1 to use.
HANSB57 said:
Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
Click to expand...
Click to collapse
Its totally impossible that patching the FlashBarService.apk could completely brick your device... A Boot loop is possible, but not a brick.
Sent from my GT-N8013 using Tapatalk HD
Flashed the wrong recovery!
Hi there, Ive soft bricked my Note 8.0 by accidentally flashing Note 2 recovery. Anyone know how I can fix this? Stuck in boot screen. I can get to download mode and Odin recognizes it, but I have no idea what to do from there.
Any advice/help would be greatly appreciated..
no problem flash the note 8 recovery with odin
Sorry but I am new to soft brick. Have 3 rooted devices and never brick before. Can put device in download mode as kennielsen but I'm lost after that. Details on what to do and how to do it would be very nice, please!
Sent from my SM-N900V using XDA Premium 4 mobile app

I really need help with this bricked tablet

Hello XDA forum, I' m really exhausted to serch on the web for solutions about my problem so I' ll explain it: I have this tablet and it doesn' t work, it bricked itself, when I start the tablet normally it stops with the acer logo, when I start it in recovery mode 2 pictures appears the first with an android that is charging something and the second with the same android lying with stomach opened with a ! inside, if I try to select any option i can't, i can just scroll between the options, so when i link the tablet to the computer the computer doesn' t recognize the tablet, so please help me a lot, I have stock ICS rom updated OTA and locked bootloader, anyone that can help me can contact me here or in facebook (Giuseppe Bosco). Thanks in advance for replies
Mulchergun said:
Hello XDA forum, I' m really exhausted to serch on the web for solutions about my problem so I' ll explain it: I have this tablet and it doesn' t work, it bricked itself, when I start the tablet normally it stops with the acer logo, when I start it in recovery mode 2 pictures appears the first with an android that is charging something and the second with the same android lying with stomach opened with a ! inside, if I try to select any option i can't, i can just scroll between the options, so when i link the tablet to the computer the computer doesn' t recognize the tablet, so please help me a lot, I have stock ICS rom updated OTA and locked bootloader, anyone that can help me can contact me here or in facebook (Giuseppe Bosco). Thanks in advance for replies
Click to expand...
Click to collapse
same thing happened to me
from what i have read most of these tablets have bad emmc chips
if it's still under warranty they will probably replace it
if not, you are screwed, just like me and tons of other people
just dont get another acer tablet
you have to make them pay somehow
stay away from asus too, ive had bad experiences with them
Mulchergun said:
Hello XDA forum, I' m really exhausted to serch on the web for solutions about my problem so I' ll explain it: I have this tablet and it doesn' t work, it bricked itself, when I start the tablet normally it stops with the acer logo, when I start it in recovery mode 2 pictures appears the first with an android that is charging something and the second with the same android lying with stomach opened with a ! inside, if I try to select any option i can't, i can just scroll between the options, so when i link the tablet to the computer the computer doesn' t recognize the tablet, so please help me a lot, I have stock ICS rom updated OTA and locked bootloader, anyone that can help me can contact me here or in facebook (Giuseppe Bosco). Thanks in advance for replies
Click to expand...
Click to collapse
OK look, if you had read the thread called "BRICK THREAD" you would know you can only either return the tab or keep it as a expensive paper weight. There's no fixing it.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Get your a100 repaired
READ this post and follow directions
http://forum.xda-developers.com/showpost.php?p=47298040&postcount=4

[Q] Bricked Galaxy W (What I did, What I get)

Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks
nemli said:
Dear Friends,
I bricked my Galaxy W. Here is the bricking procedure.
- I reset my phone with original loader and converted into original factory state.
- Than with this clean phone, I rooted it by help of this guide
It was successful. Thanks for that guide.
- Than from google play, I loaded terminal emulator and tried to load recovery-clockwork-6.0.4.5-ancora
- Rebooted my phone and surprise: My phone is dead.
What I get:
- My phone is completely unbootable.
- No key combination is working
- Completely blank screen without any indication.
- But my PC recognizes my phone as QHSUSB_DLOAD
It seems that Qualcomm High Speed USB driver fits this thing and shows COM5.
- But ODIN does not see anything.
What I need:
- HELP!
Thanks
Click to expand...
Click to collapse
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
sujithar37 said:
Are you sure that you are not able to go download mode by key combination.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.
nemli said:
I can not see anything in my phone screen, therefore I can't be sure. But since I can not see any action in PC too I may say; I'm not able to go to download mode.
(I'm not expert on this subject, I always have doubt what I talked about, sorry for that)
However as I say in my first message Qualcomm High Speed driver is always in charge as the phone plugged.
Click to expand...
Click to collapse
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
sujithar37 said:
Please refer below the link, may be that would help you
http://forum.xda-developers.com/showthread.php?t=1853385
http://forum.xda-developers.com/showthread.php?t=1551016
The only way you can get back from this situation that is you have to enter download mode and flash stock firmware. Your issue will be resolved after that. Make sure you installed Samsung USB drivers into your pc. If this doesn't help then you may contact service center.
Sent from my Xperia Neo V using xda app-developers app. Hit thanks if it helped
Donate me if you can
Click to expand...
Click to collapse
Thanks for your valuable responses. I will try what is recommended in those two links, and of course will give the feedback to here to help the (potential) brickers.
full brick
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks
nemli said:
Hello to all,
I have tried to enter with some different key combination, not worked.
I have tried USB-JIG, not worked.
Does anybody have an idea to go with QHSUSB drivers?
Because only with this, my computer recognizes my bricked phone.
Thanks
Click to expand...
Click to collapse
same problem as me
usb does not recognize my phone
if u find a solution contact me please
Solved by JTAG
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.
nemli said:
Dear friends,
I have tried all the procedures without touching phone PCB. Non of them worked.
I have decided to apply JTAG procedure. Actually this procedure is a little bit complicated for me. I have found a guy making this. And in a very short time, my phone returned back to life.
Now it is working with a Cyanogenmod release (based on Android 4.2.2.)
I have some issues but anyway, my phone is working now with better system performance.
JTAG saved my phone.
Click to expand...
Click to collapse
How much did he charge you for the JTAG? I am looking to JTAG few phones
MayB4ck said:
How much did he charge you for the JTAG? I am looking to JTAG few phones
Click to expand...
Click to collapse
Nearly 20€ per JTAG.
If someone need QHSUSB_DLOAD solution...
Maybe I can help him...
You need Qualcomm Drivers... forgotten which one exactly I have used...
QPST Version Build 411
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9
Procedure looks similar to this:
forum.xda-developers.com/attachment.php?attachmentid=2754655&d=1400627472
In this Thread I have tried many things...
http://forum.xda-developers.com/showpost.php?p=52808706&postcount=282
I could prepare files for testing for I8150...
Not tested by me nor confirmed with I8150... as only S8600 for me available...
If someony want test... PM me.
Next few hours or days I could upload files for QPST...
Code:
MBR from I8150
DBL from I8150
OSBL from I8150
Need testers and feedback please.
Best Regards
Will check my HD for Qualcomm drivers...
Maybe upload later...
Here are test files... because untested...
Risk to reach other bad status... So you could need JTAG...
Short description...
DBL and OSBL are taken from JTAG dump...
It seems chinese Version could be different...
But MBR... first 512 Bytes are 1:1 same in all I8150 JTAG dumps I have on my HD...
partition.mbn is MBR from I8150... 512 Byte
DBL and OSBL have size from partition... extracted from JTAG dump...
DBL is in partition 2
OSBL in partition 3...
Settings for QPST are hopefully visible in Screenshot...
It is mandatory to use QPST Build 411... older Versions not accept MBR as partition.mbn without header...
Header in MBR not deadly but could be bring other trouble...
For testing now only correct drivers "missing"...
I have so many stuff downloaded...
Will try to find correct one.
Again, I have only S8600 for test...
Maybe with I8150 not possible...
But before you buy JTAG you can try.
Good luck.
Best Regards
Edit 1.
Qualcomm driver to find should be not impossible... use magic search word: QHSUSB_DLOAD... for instance here:
http://forum.xda-developers.com/showpost.php?p=40072841&postcount=1
or try this one:
http://forum.xda-developers.com/showpost.php?p=40195799&postcount=7
And here again Link for working confirmed QPST Version Build 411... tested successfully by me with S8600:
http://forum.xda-developers.com/showpost.php?p=50204328&postcount=9

Phone does not turn on or charge at all, no lights/samsung logo/vibration whatsoever

Here's some background if it will help: I've been trying to install cyanogenmod on my T999L, and at one point I needed to boot into TWRP recovery mode. I got TWRP from the Play Store but when I tried the vol up-home-power thing I did not see an option for booting into TWRP on the menu, so I got Quick Boot from the Play Store and tried to select recovery. When I did this the phone shut off and since then I have been unable to turn it on. I doubt it is a battery issue since I had approx. 50-60% battery left on the phone before it shut off, but I tried recharging it anyways and it will not charge. I am not very well versed in technology so advice would be appreciated.
I've tried vol up-home-power to boot into recovery but the phone doesn't turn on or respond at all. When plugged into the charger nothing turns on and no LED lights turn on either. I have not looked at the battery because I would rather not take the phone apart.
Am I screwed or is there anything else I should try?
Connect the phone to a windows computer. You see any new devices appear in device manager? What about a devices that us named something like qhusb?
audit13 said:
Connect the phone to a windows computer. You see any new devices appear in device manager? What about a devices that us named something like qhusb?
Click to expand...
Click to collapse
Nope, no new devices.
Was the phone rooted before trying to install TWRP from the Play Store app?
audit13 said:
Was the phone rooted before trying to install TWRP from the Play Store app?
Click to expand...
Click to collapse
Yes, it was already rooted.
All I can think of is the possibility that an incorrect recovery was flashed to the phone and bricked the phone. The only way to revive the phone may be to fix it through a jtag service.
audit13 said:
All I can think of is the possibility that an incorrect recovery was flashed to the phone and bricked the phone. The only way to revive the phone may be to fix it through a jtag service.
Click to expand...
Click to collapse
Can you explain what a jtag service is and does?
http://www.forensicswiki.org/wiki/JTAG_Samsung_Galaxy_S3_(SGH-I747M)
Jtag is a method of force flashing the firmware by connect a cable directly to the phone memory chip.
audit13 said:
http://www.forensicswiki.org/wiki/JTAG_Samsung_Galaxy_S3_(SGH-I747M)
Jtag is a method of force flashing the firmware by connect a cable directly to the phone memory chip.
Click to expand...
Click to collapse
I see. Do most phone repair stores offer jtag services? For instance, could I try asking T-Mobile (my carrier) to fix it? Or should I look for a specialized place?
Most cell repair shops can jtag and the Samsung is a very popular phone. A local T-Mobile dealer may be able to fix it.
It may be cheaper to find a working phone with a smashed screen on your local classifieds.
audit13 said:
Most cell repair shops can jtag and the Samsung is a very popular phone. A local T-Mobile dealer may be able to fix it.
It may be cheaper to find a working phone with a smashed screen on your local classifieds.
Click to expand...
Click to collapse
All right, thanks for the advice!
That's an S3...if you can get it to download mode, you should be able to flash it back to stock...s3 firmware should be easily available from various sources
Sent from my SM-N920G using XDA-Developers mobile app
The OP's phone is dead which means he cannot get into download mode.
mrao said:
That's an S3...if you can get it to download mode, you should be able to flash it back to stock...s3 firmware should be easily available from various sources
Sent from my SM-N920G using XDA-Developers mobile app
Click to expand...
Click to collapse
No can do, it's hard bricked.

Categories

Resources