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.
Related
Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys
Where can I see if my phone is 791F?
i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.
tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .
链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg
Hi,
Was trying to revert to stock ROM and didn't realize you can't go back to an older firmware. Completely toast now. Doesn't go into download mode, no scree/LED light/anything.
It does show up as Qualcomm 9008 in Device Manager (Windows 10 64 bit).
I found and downloaded all the .bin files from a ZV6 stock phone but not sure how to proceed from here. I have two spare 32GB microSD cards as well. Also have a .tot file too and an Ubuntu live flash drive ready. Any help is much appreciated. Thanks
Ima Goodlady said:
Hi,
Was trying to revert to stock ROM and didn't realize you can't go back to an older firmware. Completely toast now. Doesn't go into download mode, no scree/LED light/anything.
It does show up as Qualcomm 9008 in Device Manager (Windows 10 64 bit).
I found and downloaded all the .bin files from a ZV6 stock phone but not sure how to proceed from here. I have two spare 32GB microSD cards as well. Also have a .tot file too and an Ubuntu live flash drive ready. Any help is much appreciated. Thanks
Click to expand...
Click to collapse
take a look in the h811 tmobile i think they have a way to bring it to life.
raptorddd said:
take a look in the h811 tmobile i think they have a way to bring it to life.
Click to expand...
Click to collapse
I've done that and at this point, I was able to successfully write an LS991 ZV6 dump to a microSD card. The problem now is when the SD card is inserted, I get a secure booting error 1006 and it endlessly restarts. Can't get into recovery or download mode either, it will restart.
Ima Goodlady said:
I've done that and at this point, I was able to successfully write an LS991 ZV6 dump to a microSD card. The problem now is when the SD card is inserted, I get a secure booting error 1006 and it endlessly restarts. Can't get into recovery or download mode either, it will restart.
Click to expand...
Click to collapse
well lets hope theres a way to fix this soon.
is these file are original or fake http://easy-firmware.com/index.php?a=browse&b=category&id=17384
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
aaya888 said:
http://gsmmarhaba.com/threads/unbrick-lg-g4-brick-hs-usb-qdloader-9008-without-box.612/
Click to expand...
Click to collapse
Incomplete files. I need files for non-fused devices. With files for fused devices cant write to mmc.
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....
Let me explain:
First I hard-bricked my 16gb i747 phone by accidentally flashing an old bootloader with twrp, then I debricked it using a debrick image I found online.
One day I left my phone charging over night and I woke up in the morning and found it overheated and soft-bricked again for some reason, at the time I could get into bootloader, but I couldn't flash anything, it kept giving me writing errors and pit write failure. I didn't have time to deal with it at the time so I just picked another phone.
Now --today-- my other phone --Note 3-- got bricked the same way when I tried to install linux on it, but I fixed it using a full 32gb debrick image I prepared before.
I remembered that my old phone -- The i747 -- is still bricked, so I tried to boot it up but this time the phone wasn't booting at all then after listing my usb devices I figured out that it was hard-bricked when It said qulacomm 9008, so I flashed the debrick image I found online and it booted up to bootloader but in a strange way. It says:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS.
COPY FROM T-FLASH.
BOOT RECOVERY.
WRITE 159488 sectors.
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-I747
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWERV: 3
And when I list it, it says 'I9100 (samsung galaxy s II) download mode'.
I tried various pit files for various roms and versions of the device, I tried editing the image before booting up the device, and I tried booting using every possible way, but nothing worked. I've been searching all over the internet for a full debrick image, in hope I could boot from sd card and try to fix it after that, or leave it as it is.
The phone is still overheating at the bottom --around the sdcard slot-- and I'm starting to think that this is a physical damage thing, but I really want to fix this one, please help!
Hope this can help
I personally used these files
It's just my Backup
Search for the files and verify they are what you need
https://mega.nz/#F!o5QQ2AjZ!DkFZP4K7AluKjgeeMFEkIA
Sent from my SM-N950U using Tapatalk
chowming said:
Hope this can help
I personally used these files
It's just my Backup
Search for the files and verify they are what you need
https://mega.nz/#F!o5QQ2AjZ!DkFZP4K7AluKjgeeMFEkIA
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Thanks and all, I'm definitely gonna use those files in the future, but...I discovered that my phone was toasted and the problem is with the qualcomm chip, I think that some transistor next to the chip was deformed.
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.