Database Users

[Q] Is my Tab done for? Is it fixable? Help!

I'm having the following problems with my TAB and would like to know it's fixable. I treid almost everything to fix it without success. I'm hoping someone can help me. Anyone have these problems before?
1. Doesn't charge normally. It would charge but charge really slow like it's connected via us. It shows an x next to the lightening icon when I charge it using the original charger and cable.
2. I cannot go into recovery mode. I get the black screen with the white line. There's also no boot animation when it boots up.
3. The camera doesn't work. I get a fail message when I open it.
4. My computer doesn't detect it in download mode, kies or mass storage. My computer detect my samsung galaxy s i9000 without any problems so I know it's not the computer. I cannot change the firmware because my computer doesnt detect it.
5. I dont have the receipt to do a warranty repair. What are my other option?
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build XXJMA
Any help is much appreciated! Thanks!

Did you register your Tab with Samsung?
If so, they have a record of your purchase and will be able to provide support.
If not, then try this which I got from their online chat: Hope it helps.
"Kyle: To recover the device via the hardware keys, do the following:
Kyle: 1. Power off the handset.
Kyle: 2. Hold the Vol Down Key + Vol Up Key + Power Key for 15 seconds then release.
Kyle: 3.When the recovery screen comes up, use the volume up key and volume down key to navigate through the selections and the power key to select item.
Kyle: 4. Select Delete all user data to recover the device. To confirm, scroll down and select Yes – delete all user data. The phone reboots and again displays the recovery screen.
Kyle: 5. Select Reboot system to restart the handset again. "

Thanks but I cannot get to that recovery screen like I said above. All I get is a black screen with a white line when I try to go into recovery mode. I also purchase this used with no receipt.

U just need to flash a working rom. Try roto jm... in the dev forum
Your tab was modified. I wont blame Samsung if they wont fix it for u
Sent from my SGH-I987 using XDA App

How do i flash to a different rom if a computer wont detect it?

Do you have the latest kies installed? Is USB Debug on? If it still doesn't detect, have you tried android-sdk or heimdall. Each comes with usb driver. I find it hard to believe your PC doesn't detect the tab. I never heard such thing before unless you're the real first victim then...yeah, try to call Samsung and pay a fee.

Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.

starbuck123 said:
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
Click to expand...
Click to collapse
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.

Benjamin Dobell said:
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Click to expand...
Click to collapse
Thanks for your advice but I already tried above. I didn't have any problems/trouble connecting my Verizon Tab and Galaxy S phone to the computers to change the roms. There is most likely something wrong with the Tab. I gave up and contacted Samsung yesterday. I sent the Tab to them yesterday and hopefully they won't charge me to fix it.

[Q] Totally bricked my phone with Heimdall

Hello guys!
I have totally bricked my phone with Heimdall 1.1.1. I followed the procedure to build Heimdall from source on my Arch Linux box. Then I have used the stock JVQ firmware from samfirmware.com to flash. Unpacked CODE.tar, CSC.tar and MODEM.tar and using heimdall-fronted selected following files to flash:
PIT -> s1_odin_20100512.pit
From CODE.tar:
FactoryFS -> factoryfs.rfs
Kernel -> zImage
Param.lfs -> param.lfs
Primary Bootloader -> boot.bin
Secondary Bootloader -> Sbl.bin
From CSC.tar:
Cache -> cache.rfs
Database data -> dbdata.rfs
The whole flashing procedure was successful, but the phone didn't boot at all. I don't even see the phone ! computer picture that I used to see couple of times before when I was trying to flash something with odin. Nothing. The phone is totally unresponsive. No three button combo, no download mode, no repair mode.
Note that I was never able to successfully flash the firmware from the same machine (my laptop) when flashing with odin on Windows 7. I got only the above mentioned ! computer picture and was able to get the download mode again. Then I flashed the firmware with odin on my Desktop Windows 7 machine.
What do you think about that guys? Did I do something wrong when flashing? Do I have to send the phone to Samsung for the warranty or will I be able to unbrick the phone by my self? I have read that even the USB jig which I have ordered on ebay won't work for me, since I can't even power on my phone. Do you think that people in Samsung will be able to fix it?

Hi! Sorry for my bad english...
u already have the USB jig in your hands? i have an i9000B phone and bricked it in a power failure while flashing a ROM with repartition... the phone went to the "phone!PC" screen, and after taking out the battery to try download mode it didn´t power on again. totally dead.
after a quick search in the forums i´ve found the thread about the USB JIG.
i´ve made a homemade one, as described in the thread... tooke out the battery, waited some seconds, pluged the jig in usb port, then put the battery back in... just got download mode! u must plug the jig with the phone powered down...
to make sure its really of, remove the battery, plug the jig, replace battery.
Good luck =D

frangows said:
u already have the USB jig in your hands?
Click to expand...
Click to collapse
Thank you for your reply. I still don't have the jig, just ordered it. It will ship probably next week (the weekend is coming). It might take some extra time, because is coming from US to Europe. I will let you know whether it works then.

The file -> partition mappings you listed are correct, are you sure that's exactly what you entered?
If you didn't receive an error then the files were transferred to the phone in their entirety without any problems. If a device doesn't boot after this it usually means the files weren't meant for your device (probably not the case here) or you that you accidentally put one of the bootloaders or param.lfs in the wrong spot. This is one reason why I'm hoping Heimdall Firmware Packages will be adopted.
Even if you can't see the screen working try charge your phone for a bit, 3-button combo and then see if your PC detects the phone. I recently read that sometimes a corrupt param.lfs might simply cause your screen to stop working rather than hard-bricking the whole device, although I can't confirm this.
A custom jig is still worth a shot, as it causes your device to boot using a backup secondary bootloader. So if the problem is with the secondary bootloader then the jig will allow you to access download mode.
However if the problem is with boot.bin or param.lfs then a JIG probably won't work and you'll need to take your phone into a Samsung Repair Centre. Either that or send your phone to someone who can perform a JTAG repair, the former tends to be much simpler.

Benjamin Dobell said:
If you didn't receive an error then the files were transferred to the phone in their entirety without any problems. If a device doesn't boot after this it usually means the files weren't meant for your device (probably not the case here) or you that you accidentally put one of the bootloaders or param.lfs in the wrong spot. This is one reason why I'm hoping Heimdall Firmware Packages will be adopted.
Click to expand...
Click to collapse
I'm pretty sure I did everything right (but you can't be always 100% sure). I still think there is something wrong with USB ports on my laptop. When I was flashing with odin on the same laptop in win7, the flashing procedure was successful, but I got the "phone!computer" picture and was able to get into download mode again. Fortunately, I flashed only kernel and not the whole package with bootloader. Then I used my desktop computer to successfully flash the firmware again.
Benjamin Dobell said:
However if the problem is with boot.bin or param.lfs then a JIG probably won't work and you'll need to take your phone into a Samsung Repair Centre. Either that or send your phone to someone who can perform a JTAG repair, the former tends to be much simpler.
Click to expand...
Click to collapse
I will wait for my ordered JIG and if it won't work, I'm going to take the phone to Samsung. Any way, I will never try to flash anything to my phone from the laptop. The desktop computer way seems to be the better way.

Well, I almost forgot I have posted here. The JIG didn't work for me so I had to send my phone to the service. After three weeks phone came back. They had to change a defective part of the phone. I don't know which part it was (it was the state of e-shop, where I bought the phone).

Flashing primary bootloader is generally a dangerous thing to do.

http://forum.xda-developers.com/showthread.php?t=1236273
or you could've helped these guys out

Hot To Unbrick Galaxy S JIG Method
this is a giude
I test this guide 1 month ago and it works

[Help pls] Note 3, not responding: Bricked? Installing Lineage OS

I just bought a BNIB Note 3.
Samsung Note 3: SM-N900W8
Symptoms: Won't turn on, no lights, no load screen, no recovery mode, no download mode.
When I hook the phone up to the PC via USB it does vibrate and sounds the connection ringtone
What I was doing when this happened:
I had just recently rooted using "KINGRoot" - checked root and it was successful
I installed "TWRP" and booted into recovery mode and it was a success as well(I didn't actually run here yet)
***I installed and opened "Flashfire" to Flash the LINEAGE OS to my Rom buuut I didn't actually select the Lineage pack and I accidently pressed FLash(insert expletive here) *****
So Flashfire went through it's loading and when it was done it shut off and then the symptoms started.
It's a Note3 from Bell with all of their bloatware on it and I wanted to clean it all off and run a clean/efficient Note 3 cell with Rogers. I'm not looking to keep any of the data currently on the phone as there isn't anything currently on it. I just want to be able to install Lineage and use my Note.
I've searched for 30 hours pretty solid so far and unfortunately I haven't come across a clear solution. Can anyone give me a diagnosis and a tutorial or a link to a fix.
I'm open to loading from MicroSD, USB Jig, Samsung Kies....anymore information you require from me as away and I'll get back ASAP

Dead battery would be first check .

JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
Battery - I did the "spin" test on the battery and it doesn't show any physical characteristics of an overheated(bulged) battery. I'm going to test fit my battery into another note3 and I'll respond asap.

JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
I tried the battery in another Note3 and my battery is 52% charged and had no issues booting the tester phone.
I have the phone being tested for any Hardware issues right now.
If it's not a hardware issue will I be able to force a Rom(whether OEM Firmware or other) to install via MicroSD or USB jig?

When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.

audit13 said:
When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.
Click to expand...
Click to collapse
No, the PC doesn't see the phone.
The USB jig or MicroSD force is something I'm researching to try next(feel free to provide any good links to set up a jig(I've done this with Ubuntu on my laptop but this has a more intimidating feel to it)). The Tech at the shop I took it to test the hardware says "the motherboard" is broken and he'll fix it for $60.
For future considerations I'll learn to use TWRP flashing ROMs.

If the shop is offering to fix it for $60, they may be just force-flashing the firmware with something like an Octopusbox.
The USB jig may force the phone into download. If it doesn't, I don't think you'll have a choice but to pay to have it flashed. Unfortunately, Samsung will not help as rooting would trip the knox counter.

USB jig ebay are the usual cheap source.

Lenovo Tab 3 8 (TB3-850M) - Hard Bricked

Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.

wxtester said:
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
Click to expand...
Click to collapse
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.

AeonFlux1603 said:
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
Click to expand...
Click to collapse
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course

wxtester said:
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
Click to expand...
Click to collapse
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.

AeonFlux1603 said:
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
Click to expand...
Click to collapse
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...

wxtester said:
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
Click to expand...
Click to collapse
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.c...-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:

I have the same issue. I dont know how but i got hard bricked completely. I was flashing rom on it and it got bricked. Now service centre guy is saying that i have to change motherboard altogether. But your post seems convincing. Please let me know the next detailed process.

i have the same issue.
one day stop working

AeonFlux1603 said:
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.cdn.ampproject.org/v/s/forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/amp/?amp_js_v=a2&amp_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&amp_ct=1551037935701&referrer=https://www.google.com&amp_tf=From %1$s&ampshare=https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
Click to expand...
Click to collapse
what is next? i have a tab 3 710f that is very dead.. hardbricked in wont boot into nothing.. black screen like its shut down

[SM-T585] Have I completely bricked my tablet? And is there something I can do about it?

So one day I wanted to install PostmarketOS and I managed to get the ZIP file to flash in TWRP, but it didn't work. Idiot me decided to extract the boot img and flash it onto the boot partition and now it's stuck on the boot logo "Samsung Galaxy Tab A6 blah blah...". I tried to get into recovery but to avail, even download mode too.
Well, with all that... Is it possible to somehow trigger an emergency download mode or since I took the back off the tablet, is there any pins that could short in order to reflash the EMMC? Here, I've attached some pics.
Let me know if all hope is lost and I have to get a new mobo. Thanks!

anon2003 said:
So one day I wanted to install PostmarketOS and I managed to get the ZIP file to flash in TWRP, but it didn't work. Idiot me decided to extract the boot img and flash it onto the boot partition and now it's stuck on the boot logo "Samsung Galaxy Tab A6 blah blah...". I tried to get into recovery but to avail, even download mode too.
Well, with all that... Is it possible to somehow trigger an emergency download mode or since I took the back off the tablet, is there any pins that could short in order to reflash the EMMC? Here, I've attached some pics.
Let me know if all hope is lost and I have to get a new mobo. Thanks!
Click to expand...
Click to collapse
You can refer to the video wherein the device is S20 FE but you will need to use EDL cable to get in the edl mode.

mvikrant97 said:
You can refer to the video wherein the device is S20 FE but you will need to use EDL cable to get in the edl mode.
Click to expand...
Click to collapse
Interesting, but my tablet's CPU is an Exynos 7870 Octa not a Qualcomm, not sure if it would work. Also, is it possible to make such EDL cable at home? Oh, and what about software, what do I need to use in order to reflash the stock ROM or at the very least bring back Download Mode? (I assume Odin wouldn't work?)

anon2003 said:
Interesting, but my tablet's CPU is an Exynos 7870 Octa not a Qualcomm, not sure if it would work. Also, is it possible to make such EDL cable at home? Oh, and what about software, what do I need to use in order to reflash the stock ROM or at the very least bring back Download Mode? (I assume Odin wouldn't work?)
Click to expand...
Click to collapse
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com