Database Users

phone will not turn on after restore with Heimdall

my phone will not turn on after successfully performed a restore backup with Heimdall
the backup are the Original from Factory....
whats happen i try to charge my phone, and the screen doest show any sign of life
it doestn boot it doesnt charge, it cannot opened by me
heeeeeeeeeeeeelllppppp

If Heimdall didn't give you any errors then the flash went through fine. Are you sure that you flashed files that were meant for your particular model of Galaxy Tab?
Given the information you've given about the device not turning on or responding at all, it seems as though you've flashed a bootloader that was not designed for your device. You can try create a custom jig and it may be able to boot your device into download mode using the backup secondary bootloader. If that doesn't work then the only other fix is a JTAG fix which is best performed by Samsung themself.

i put in First Boot Loader
boot.bin
i Put on Secondary Boot Loader
Sbl.bin
any mistakes here? these files are recovered from my Tab with Roto BackUp
any chance to do it in da house and not from Samsung Warranty?
Benjamin Dobell said:
You can try create a custom jig and it may be able to boot your device into download mode using the backup secondary bootloader.
Click to expand...
Click to collapse
HOW to do IT ??? explain me more steps

i found this video for make cable for samsung captative......
http://www.youtube.com/watch?v=Rdn5GoRjhn0
what type of cable i need to do the same on my Tab???
anyone can tell me any steps please??

Maybe try this:
http://forum.xda-developers.com/showthread.php?t=885919&highlight=reset+battery

interesting information but i need to research much more
http://forum.xda-developers.com/showthread.php?t=819551
Reediting:
I try with Android SDK and ADB reading this little tutorial
http://mingersoft.com/blog/2010/09/samsung-galaxy-s-why-download-and-recovery-modes-are-missing/
When I plug it into my computer it tries to install a driver for "SEC S5PC110 Test B/D"
any one have a copy of this driver, or can create one for this proposit????

Does the device power on and show anything on the screen? If the Tab won't even turn on then you are bricked but not to worry.. I did the same to mine, and samsung has repaired the device and its on its way home to me today.

i think the better idea is call samsung, wait 2 or 3 weeks.......
but i want know more about some info posted in this thread
perhaps, how and where are the first person whit this Driver, or the first or second with a custom cable jig Compatible with Galaxy Tab and can post where are the steps to do it in da home

asus tf300t bricked

kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance

Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?

techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!

Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.

Hard brick SM-N910F

Tried installing custom recovery didn't work out like I had hoped now im stuck with a phone that isn't detected by odin or kies but by MiFlash
Please tell me there is something I can do to fix it or get it to some sort of working order..? Is there a jtag tool or usb jig I can use?
Update - I found out the phone was still under warranty so I sent it away to be repaired. It was repaired and I now have a working phone !

ylmcc said:
Tried installing custom recovery didn't work out like I had hoped now im stuck with a phone that isn't detected by odin or kies but by MiFlash
Please tell me there is something I can do to fix it or get it to some sort of working order..? Is there a jtag tool or usb jig I can use?
Click to expand...
Click to collapse
What have you done to reach that state? I know that you're desperate but you must give some details if you want help.

It was given to me with 5.1.1 installed however it failed mid process and while on 5.1.1 it kept freezing and acting weird such as boot with weird errors and they only appeared after it was updated, I decided to root it with odin and it never fully rebooted after the was root applied. I finally got it to boot to stock and rooted and decided to install a custom recovery which was twrp while selecting the recovery it said if its a wrong location it will brick, with this in mind I checked the model with the one on their site and it seemed to make sense and applied it.
This caused the original problem which made it boot straight to download mode with it saying it could not normal boot. I then googled the problem and one said the pit was corrupted and downloaded the correct file. I then applied this through odin with stock firmware and it refuse to flash. At the time I was thinking a restart on the device would help, but it resulted in not booting at all and not being detected....
It does not light up or make a vibration when its connected or powered on if there is any solution it would be great...

Can anyone help or point in the right direction?

Hard brick SM-910F
Hello! If this is the good recovery for the N910F he would have from start.
Try to boot via the recovery flight up + home + power.
If you TWRP flash a custom in a first time rom

[email protected] said:
Hello! If this is the good recovery for the N910F he would have from start.
Try to boot via the recovery flight up + home + power.
If you TWRP flash a custom in a first time rom
Click to expand...
Click to collapse
Nothing however the pc did detect a new driver called qualcomm hs-usb qdloader 9008

ylmcc said:
Nothing however the pc did detect a new driver called qualcomm hs-usb qdloader 9008
Click to expand...
Click to collapse
qualcomm emergency download mode. is it called.

Tunestwo said:
qualcomm emergency download mode. is it called.
Click to expand...
Click to collapse
Anything I can do to get some sort of os on the phone now?

in this case via Odin tries to reinstall the tar of the official rom N910F .

ylmcc said:
Anything I can do to get some sort of os on the phone now?
Click to expand...
Click to collapse
Can you tell us if you can get on recovery screen, either TRWP or stock, or download mode.

You could try installing these drivers:
https://www.androidfilehost.com/?fid=24499762636000789
Reboot just in case and try to connect your device again.
(In download mode, with the key combination)

mangui said:
Can you tell us if you can get on recovery screen, either TRWP or stock, or download mode.
Click to expand...
Click to collapse
The phone does not display or respond when the keys are pressed, just a black screen..
Battlehero said:
You could try installing these drivers:
https://www.androidfilehost.com/?fid=24499762636000789
Reboot just in case and try to connect your device again.
(In download mode, with the key combination)
Click to expand...
Click to collapse
Chrome detected a virus in the rar

ylmcc said:
The phone does not display or respond when the keys are pressed, just a black screen..
Chrome detected a virus in the rar
Click to expand...
Click to collapse
Really? I just scanned it with VirusTotal and it is clean.
Virus Total Results
32Bit.exe scan results
64Bit.exe scan results

Battlehero said:
Really? I just scanned it with VirusTotal and it is clean.
Virus Total Results
32Bit.exe scan results
64Bit.exe scan results
Click to expand...
Click to collapse
I'll download it again but windows defender detected it too.
Edit - Yep did it again, here is a link to a photo of what I get but from virus total I don't get why its being flagged perhaps false positive ??

Update
Found a jtag service that is cheap will update once I get it back...

sm-n910f
I got a brick note 4 and i want to fix it
I search over the internet for this solution and found a method
Sd card repair boot but it did not work at all
I need help
thank you in advance

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

Need Debrick image / help?

Recently rooted my galaxy s10+, seemed to work fine at first, just the camera app causing the phone to crash, right now it's in a constant reboot loop where i can't enter recovery or download mode.
Phone is instantly rebooting when I plug in a usb cable so adb won't recognize the device nor will my pc in general.
Read up on a lot of threads online & what got recommended on older threads was booting from a debrick image off of your sd card, although i'm unsure if this'll work. regardless not that I can no longer boot the phone I'm unsure of how to generate this file to begin with, which is why I was hoping one of you guys might be able to help me out with generating or linking me to said debrick image.
Or if anyone knows of another way to possibly fix my phone, please do let me know.
Thanks in advance,
A galaxy s10+ user

I don't think there is a debrick image for the S10 or S10 plus. You might want to try flashing your stock firmware in Odin.

Not sure how I am supposed to flash it without having acces to Recovery or Download mode. Any suggestions

You can't get into recovery or download mode? Sounds like you might be hard bricked then. In that case, a phone repair shop might be your best bet.

Carry on with key combi v down and Bixby plus power
Sent from my SM-G975F using Tapatalk