Develop Bugs

Please Help. S3 T999 Completely Dead

I have a Samung S3 T999 T-Mobile.
It is completely dead. It does not showing charging, It does not go to Download mode and no recovery mode too. Please help me :crying::crying:
I tried to debrick it using THIS link, but no success. Does it require class 10 sdcard only?? I tried using class 2 sdcard

Rahil S said:
I have a Samung S3 T999 T-Mobile.
It is completely dead. It does not showing charging, It does not go to Download mode and no recovery mode too. Please help me :crying::crying:
I tried to debrick it using THIS link, but no success. Does it require class 10 sdcard only?? I tried using class 2 sdcard
Click to expand...
Click to collapse
When you boot using the SD card method are you getting the following:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 159488 sectors
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
I am in similar situation. So far I have not found a solution for this after searching this forum. Others are experiencing the same, but no one has actually said what it is exactly and how (if any) we can fix this issue? Why it boots into this recovery boot mode? Why it is showing "flash write failure"? etc.

Note II GT-N7102 16GB Dual-Sim Soft-bricked Help (& files) needed

Symptoms:
1. Boot loop. GT-N7102 logo comes and the device reboots.
2. Can go to download mode. Model no. GT-N7102 is visible
3. Recovery mode-Android shows up for ~4 seconds and then phone reboots and goes into a boot-loop.
Was running N7102ZCUEOJ1_JB43_deodex_gapps_root_noknox_lite_by _neopunk88 (since March'16), when the phone suddenly decided to go into a boot-loop.
The phone was rooted. I had installed LSpeed the previous night and had set it to run in recommended mode.
What I have tried so far
1. Odin 3.07, 3.09 etc
2. stock recovery flash fails
2. tried to flash N7102ZCUEOJ1_N7102CHNEOJ1_N7102ZCUEML1_HOME.tar.md5 (last stock), but fails
3. After I had exhausted possibilities, tried the following pit files, one at a time, first from here and then here and then here along with the stock ROM. All pit files seem legit and the correct ones, but I have no way to verify. I have tried first without and then with re-partition option selected in Odin. Flash fails.
4. All drivers, USB ports and cable okay as I can flash my wife's S6.
Phone still going into download mode.
Odin fail modes
1. without pit file, while flashing either recovery or stock rom, Odil fails just after sboot.bin at NAND write-start.
2. with pit file and re-partition checked, Odin gets stuck in "get pit file for mapping"
3. with pit file but re-partition unchecked, Odin fails is the same as (1)
4. I have tried setting Odin compatibility to XP but it does not result in anything different. I haven't needed xp compatibility setting this while flashing anything before.
Please could I have some guidance on what options I have left and the files, if I am not using the correct ones?
My belief is that if I can get to the download mode, there has to be way to un-brick the phone..fingers crossed.
Thanks in advance.
UPDATE: Fixed phone by replacing the motherboard from here. Everything working fine now.

still waiting for a response..

@jam_27 It is possible that eMMC got corrupted. (it's a hardware fail)
If I were you I would try to flash TWRP. http://www.twrp.me - For N7100, as it doesn't matter for recovery.
READ: http://forum.xda-developers.com/galaxy-note-2/help/nt7100-wont-boot-wont-charge-recover-t3504290

Thanks, TWRP recovery flash fails at NAND write start.

jam_27 said:
Thanks, TWRP recovery flash fails at NAND write start.
Click to expand...
Click to collapse
Below the JTAG tool report from FoneFunShop UK
eMMC Flash Memory Chip is damaged
===============
= JTAG REPORT =
===============
Open serial port...OK
Connecting to the RIFF Box...OK
Connecting to the dead body...OK
Detected dead body: DETECTED
Set I/O Voltage reads OK, TCK Frequency is OK
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Flashing the dead body...
No Resurrection Data is available for the eMMC Chip with Capacity = 0B
ERROR: Failed use to Resurrection Data for the eMMC Chip with Capacity = 0B
ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
----
I wont be able to replace the emmc chip myself (don't have the correct tools) but should be able to replace the motherboard.
Any other suggestions before I open up the until.

Note 2 GT-N7100 stuck on boot screen

Hi, i have a problem with my phone,latest stock rom,no root,i found it stuck on boot screen after i use a non original cable with original charger, is SDS or i can fix it? when i try to use odin with stock rom i get nand write fail everytime ,i see the phone conected in device manager(photo) , in recovery i see red errors and when i enter in download mode odin see the phone but is unable to write, can you help me to fix this or any solution to fix it with usb or sd card only because i dont have profesional tools (box)? thanks

What is the Odin error? You can see it in the log.

audit13 said:
What is the Odin error? You can see it in the log.
Click to expand...
Click to collapse
nand write start fail

What file is Odin trying to flash when it fails?

audit13 said:
What file is Odin trying to flash when it fails?
Click to expand...
Click to collapse
with heimdall-suite i extract the pit file from the phone successful but i unable to write, adb slideload is recognized with adb,any command to send via adb slideload or via download mode to mount the partitions? when i send a zip file via adb slideload i get unable to mount cache,with sd card boot recovery can i fix this?

Odin is failing when trying to flash sboot.bin because you are using the wrong ROM, the ROM has bootloader that is older than the bootloader in the phone, you need to use the original Samsung USB cable, or a different USB 2.0 port.

audit13 said:
Odin is failing when trying to flash sboot.bin because you are using the wrong ROM, the ROM has bootloader that is older than the bootloader in the phone, you need to use the original Samsung USB cable, or a different USB 2.0 port.
Click to expand...
Click to collapse
the stock rom i try to flash is the latest and same with the rom from the broken phone

Sounds like the memory chip is defective.

audit13 said:
Sounds like the memory chip is defective.
Click to expand...
Click to collapse
if i try this guide from the rar file can i fix it? i only need a bootloader dump file from a working n7100 with 4.4.2 firmware and then i write it on a sd card , this will repair the nand write fail? maybe the bootloader is corupt and is working after re write with sdcard mode.

If the nand is defective, no software is going to fix it.
If the bootloader was corrupt, Odin would flash over the existing bootloader could fix it.
Try this: flash twrp to the phone using Odin and then use TWRP to flash a CM ROM to see if the phone will boot with CM.

nand write start fail with twrp and Odin

My conclusion is that the memory is defective but you won't know for sure until you have a cell shop try and force flash the firmware.

geoweb29 said:
Hi, i have a problem with my phone,latest stock rom,no root,i found it stuck on boot screen after i use a non original cable with original charger, is SDS or i can fix it? when i try to use odin with stock rom i get nand write fail everytime ,i see the phone conected in device manager(photo) , in recovery i see red errors and when i enter in download mode odin see the phone but is unable to write, can you help me to fix this or any solution to fix it with usb or sd card only because i dont have profesional tools (box)? thanks
Click to expand...
Click to collapse
if your hard is 16 gig , i am sorry to tell you it is 99% EMMC
I think PC will not solve this problem , you need to flash your phone via box if it fail you need to change EMMC
at last I wish I am wrong
Regards

xcorona said:
if your hard is 16 gig , i am sorry to tell you it is 99% EMMC
I think PC will not solve this problem , you need to flash your phone via box if it fail you need to change EMMC
at last I wish I am wrong
Regards
Click to expand...
Click to collapse
4 months ago before SDS i used emmc brickbug check to scan the phone and the status was Yes,insane chip (photo)
i manage to make a usb jig(photo) and with this i see Factory mode in download mode but same problem with nand write fail, i have to search a new motherboard

may I advise you to look at tutorials in youtube about replacing the mother board it is (solderless job) but it is not easy
you can check them to see the processing of the work , then you can judge by your self if you have the time and the ability to go forward and pick an used phone with smashed screen (choose 32 giga hard)
then you can replace the motherboard
at last I hope all your matters will be fine
Best Regards

I see at this Q&A many people have same problem, My phone just like your now, hope you can fix it, it'll help me alot
I'm still trying to take my phone's storage back, it's 0GB right now .

why does so many note 2 SDS's at this point? mine does it too, it first occured a few weeks back, it was a small issue where some folders wasn't deltable in data, but it was fine i could still use the phone and it functioned normally, untill 4 days ago, i exprienced serious issues, the so corrupted folders in data caused alot of problems, it made the phone randomly freeze, force stops apps, then this day it got more serious than ever, nothing mounts on TWRP, no not even the SD card (SD Card still works tho on my PC) odin nand write failed, i checked a few months ago with the app, it was yes a Insane chip, so i guess its time to say goodbye to my note 2 and move on, it was a great 4 years with this phone, and i am sad to see it go....

"WIP" Debrick / Unbrick T560NU-Galaxy-TAB-E / Qualcomm APQ8016 CPU

First......This is a work in progress meaning it is not a fully working solution yet.​
So that's the bad news.
The good news is that this provides an opportunity to learn something.
Everything we learn should also apply to any of the newer Samsung Qualcomm Based Devices.
Lets investigate some of the past methods used to unbrick dead samsung devices.
Also please note that these methods are for Hard Bricked Devices. ( NO Download Mode / NO Recovery Mode / Unresponsive )
Any device that can boot into download mode can easily be fixed with ODIN.
#1) Methods of possible DeBrick That I know of.
A) Use Recovery SD Card.
B) Use Firehose to flash in QDL 9008 / 9006 mode.
C) Boxes - JavaCard - Hardware type solutions.
For now lets look at option A). Hopefully this option is still viable. Although I have tested this a little and so far I am still unable to get booted into download mode.
So in researching Debrick image or Debrick rom of samsung devices you will find some things.
This is what we are interested
https://www.scribd.com/document/272...de-Qualcomm-APQ8084-Includes-SM-N910F-Rev-3-0
Looking at that we should be able to use ODIN and select T-Flash to create the Boot-Recovery-Image.
Unfortunately I tried this and it did not work. The T-Flash just hangs and eventually errors out.
This could be due to the version of Odin i used.
I tried a couple of different Odin versions without any luck.
And also YES you have to do this on a working device.
Since the ODIN method didn't work I know from past experience how to make a bootable EMMC Clone onto a SD-Card.
You can do this in windows or in linux or in the device Terminal ( TWRP Terminal)
This command will make a byte for byte copy of the device EMMC onto a SD Card.
Here are the steps.
1) Insert Blank 16GB SD card into the working device. ( The sd card must be high quality Like V30 or U1 Class. " 95 to 100 mbs speed " )
2) The bootloader version of the device you are using to make the sd card has to match the version on the bricked device. (Flash good device with odin to match factory software before making sd card) <-- <-- <-- " Probable reason my Card is not working yet to boot my bricked device "
3) After that its pretty simple.
We know that the main EMMC of the Tablet is MMCBLK0
We know that the SD Card is assigned MMCBLK1
So executing the following command will clone the emmc to the sd card.
Code:
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
It will take between 30 min and a hour to copy.
I have created this image and tested it but no luck yet.
The image is of the factory T560NUUEU1CQK2_T560NUXAR1CQK2 firmware.
I bricked my tab by flashing the aboot.bin alone from COMBINATION_XAR_FA51_T560NUUEU1APH1.
I flashed just the aboot without flashing the rest of the booloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
So what i need to do next is make a card that has the complete set of bootloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
Once we have a clone of the emmc we can flash seperate partitions on the sd card just like if we did on the device.
I know for sure the bootloader versions have to match. This is a likly cause for my card not to bring my Tab back to life.
Another possibility is that the card has the whole emmc backup. Mirror of the device. Realistically it should be just the bootloaders.
I have looked at some of the boot-recovery images for other devices. Some have only the bootloaders. Some have all the partitions but only the bootloaders flashed. And even the fact that it is a direct copy of the emmc and not its own unique GPT could all factor into it not working at the moment.
All these different combinations of things could be the difference between the card working or not working.
I will upload the image for you if you want to test it.
You can also dump each partition to an individual backup image in case you need any of them.
Do it in linux using "dd" or do it on the device using "dd" and mmcblk1 rather than mmcblk0
If you don't know what i'm talking about don't worry. I will go over things like that at some point in time.
Here is a upload of the SD Card - EMMC Clone for 16GB T560NU
http://www.mediafire.com/file/5m0b7r11nc3nn5q/16GB-T560NU-.img.zip/file
Unzip the file.
Use win32diskimager to flash the image to the sdcard.
After win32diskimage is complete a bunch of file windows will pop up. On windows 10.
It will say disk must be formatted. Do NOT format the disks.
Close them all and remove the sd card from the computer.
Put sd card in bricked device.
Plug in usb.
Try to boot.
Try to boot into download mode.
Let it sit 5 or 10 min.
See if anything happens.
If you have any luck please let us know.

Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.

BigCountry907 said:
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
Click to expand...
Click to collapse
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted

iBowToAndroid said:
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
Click to expand...
Click to collapse
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.

BigCountry907 said:
I believe you have to flash the whole bootloader set if your going to flash bootloaders
Click to expand...
Click to collapse
Correct, with qualcomm devices the revision of aboot needs to match the sbl.
Sbl checks the version of aboot if it doesn't match it refuses to boot.
Been there done that.
However I have yet to attempt a hardware repair. Debrick images unsuccessful, no response.
My next step(when I can be bothered to get around to it) is to use an sd card adapter wired directly to the emmc as both use the same protocols and an sd card controller should be able to communicate with an emmc.
As long I can get the partitions to show up on the EMMC, should hopefully be a case of flashing the correct aboot to the right partition.

BigCountry907 said:
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
Click to expand...
Click to collapse
It's only ever been on bootloader rev 1, so i figured i was fine going back as far as possible with aboot, like how it is for sboot on Exynos. Obviously not correct though.
Yeah, I dumped to an SD, but only did the first 200MB, instead of an entire image. I have no idea if that even works on this model - I was just hoping it would, like it used to for the S3 and other devices.. I have no idea where i'd get the firehose so this might be SOL

respected brother plz give me your whatsap no# my tablte t560nu dead after flash
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995

SM-T560NU Does not Turn On After Software Flash
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?

Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
If it won't even turn on, then it's hard bricked - not soft bricked. And no, no proven method to fix it

Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.

ashyx said:
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
Click to expand...
Click to collapse
I'm sure he meant aboot

iBowToAndroid said:
I'm sure he meant aboot
Click to expand...
Click to collapse
Well if he flashed aboot without sbl then there's not much hope.
SBL checks the integrity of aboot and if it doesnt match it refuses to proceed.
Can't even use qualcomm low level tools.
The only way that may be possible which I have never tried is to wire the emmc direct to an sdcard adapter and hope the controller is able to boot it and see the partitions.
Then flash the correct aboot or sbl.

Urgent help for my A5 2017 (A520W model)

I tried using the XDA Discord server to get a quick response, but apparently, some people just ignore me or don't even know how to help me. So I will try here...
I was following that tutorial so that I can use Joycon Droid on my phone. I installed TWRP Recovery and gone in his recovery mode. I wiped what the tutorial asked to wipe and began the flash process. Unfortunately, I mistakenly downloaded the flash files on the computer. I tried removing my SD Card and putting inside it the files I need, but TWRP was not able to read any data for the SD Card. So I tried to find a way to cancel the recovery menu, and I did by clicking Reboot System. Since then, my phone was locked in the logo screen. After many attempts, I've gone from the charging screen and finished by the "An error occurred while updating the device software.". I can enter the download mode, but nothing else. My phone is an A520W and I think the root was not properly installed. I researched everywhere without any solution, so I came to this discord server, hoping someone would save my phone. I tried flashing the official A520W OS, but Odin always does a FAIL message or freezes. I later tried to use another firmware file, reinstalled the Samsung USB driver and Odin, and know it says on the Download Mode screen:
SV REV. CHECK FAIL(BOOTLOADER) DEVICE: 9, BINARY 7. (it failed)
Can someone help me? I really need help!

Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)

matkali said:
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
Click to expand...
Click to collapse
Kay I'll try the easy-jtag, but if it doesn't work, who is an expert at emmc programming stuff?

Is there a way to fix the crushed partition table without buying stuff?

Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop

Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
better than the error screen right? the program name is fonepaw

Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
It is dangerous for your phone, because every phone have different partition table and different architecture!
Pit file in a520w stock firmware have partition table structures information. (use PIT_Magic.exe to see)
In old architecture of Samsung(e.g. s3) when partition table cleaned from emmc (phone internal storage), they use micro sdcard to boot from it! (to identity correct info for Odin) (same boot from USB when you are installing windows.) then by going to download mode they flash stock Rom!
But I suggest to you find one knows enough information and requirements stuffs.