Develop Bugs

Hardware failure? Hard brick? Hope?

Hello people,
I'm actually trying to help a friend who bricked his GNex while trying to flash primela03 bootloaders.
Volume + Power combos don't work anymore, the screen doesn't turn on at all (not even the exclamation mark "soft brick" symbol)... so I figured I would try this jig that I have, which worked on pretty much every Samsung Android phone that I've flashed.
But in this case there was no effect. The screen still doesn't turn on, the battery doesn't warm up while plugged to the charger, and the phone in general does not manifest any signs of life.
The last thing he saw before the phone gave up the ghost was the following :
Code:
# fastboot flash bootloader bootloader-maguro-primela03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.398s
But I don't think this is enough to send a phone spiraling to hell like this.
I've been looking around here, but this seems to be a rather rare case. So... RMA?
Cheers,
Antonius Maximus.
--

I would try to use ODIN and bring it to complete stock everything at this point. As word of advice ODIN WILL also wipe the SD card partition so all of your friends data will be gone...

MisterEff said:
I would try to use ODIN and bring it to complete stock everything at this point. As word of advice ODIN WILL also wipe the SD card partition so all of your friends data will be gone...
Click to expand...
Click to collapse
As I implicitly stated above, the phone doesn't respond to anything, not even a USB jig. So, getting to Download mode seems impossible at this point, making Odin useless.

Does it show up in Device Manager at all when plugged into the computer?

Last option before JTAG would be attempting an OMAP Flash. As long as it recognizes without a battery while plugged into the computer.
http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/
I use it all the time. I can fix about 4/5 bricks with this - if it doesn't, the processor is fried.
Good luck!

Naezor said:
Last option before JTAG would be attempting an OMAP Flash. As long as it recognizes without a battery while plugged into the computer.
http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/
I use it all the time. I can fix about 4/5 bricks with this - if it doesn't, the processor is fried.
Good luck!
Click to expand...
Click to collapse
Exactly, this is the way to go.
If nothing else responds then this is your only option, otherwise its pretend it got fried in an ota.
And that's fraud, we wouldn't do that now would we.......

So you can't reach the boot loader??? =\
Not even get the screen to turn on???

DLD511 said:
So you can't reach the boot loader??? =\
Not even get the screen to turn on???
Click to expand...
Click to collapse
Nope, the phone is truly unresponsive. My friend is bringing the device over tomorrow, I'll attempt the OMAP Flash and post the results here.

Man what to do there.....
I have like 8 different ways to fix this if you could just get that bootloader. But if you did you'd probably fix it in no time.
Sent from my Galaxy Nexus using XDA

I have to say this phone is puzzling me more and more. I have never encountered a case like this.
So, the good news are : the OMAP flash resurrected the phone.
The bad news are : I can't get into fastboot or recovery. I get the Phone -- Triangle -- Computer symbol on the screen, which I have never seen before on a Galaxy Nexus (only on Captivates, GS1 and GS2).
So I figured I could use Odin 1.85 and flash Chainfire's stock images. But this is what I get :
Code:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> bootloader.img
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Removed!!
As soon as it tries to flash the bootloader portion of the tar file, it hangs and fails after a few seconds. Then the phone reverts to its completely unresponsive state, and I can only get it back to life with another OMAP Flash.
I've done quite a few phones before, but this one leaves me baffled.
Anybody has seen this before?

So here's the final situation...
Here's the current status :
OMAP Flash resurrected the phone
No access to bootloader, download mode or recovery
<Phone--Triangle--Computer> symbol appears regardless of Pwr/Vol key combos
USB Jig has the same effect : <Phone--Triangle--Computer>
Odin recognises the phone
Odin fails to flash anything, getting stuck at NAND Write Start, no matter which partition I try to flash
Checking Repartition and using partition-table-0915.pit on Odin has the same effect, getting stuck at NAND Write Start
To disqualify enthusiasts' advice, here's what I have done so far :
I have used every possible driver that I know of (PDAnet, Kies, GNex Toolkit), but Odin still doesn't get past NAND Write Start
I have used multiple USB cables, including the original GNex cable
I have tried to flash Chainfire's all-in-one Odin package
I have tried to flash the original firmware
I have tried to flash each partition individually (bootloader/radio/pda, etc)
TL;DR - Phone is stuck in <Phone--Triangle--Computer> no matter what I try, and Odin fails to flash.
At this point, I need some major help.

Not sure if I can be of any help, but here goes:
The <Phone--Triangle--Computer> is download mode. At least this is a start.
The only partition that you need worry about at this point is the bootloader. All the others can be flashed from that.
Given that odin is not downloading the bootloader to your device, i only see two possibilities: 1) the physical NAND is corrupt, or 2) that something is messing up when you are trying to use odin.
1) Are you using odin v1.85?
2) Did you do the following step IN ORDER?
1. Enter download mode on your device.
2. Launch ODIN software
3. Press the PDA button and select the .tar file.
4. Make sure in ODIN that "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
5. After the above, then connect your device to your computer.
6. Press the "Start" button.

efrant said:
1) Are you using odin v1.85?
2) Did you do the following step IN ORDER?
1. Enter download mode on your device.
2. Launch ODIN software
3. Press the PDA button and select the .tar file.
4. Make sure in ODIN that "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
5. After the above, then connect your device to your computer.
6. Press the "Start" button.
Click to expand...
Click to collapse
Yes to all, of course. This is far from being the first Samsung phone I flash (even though I admit I never had to use Odin for a GNex).
However, I did wipe and repartition the phone with its PIT file, and that allowed me to access Fastboot after an OMAP Flash. So, new development : I got to Fastboot!
However...
Of course it tells me that there's no bootable ROM, and that's fine. Any command, and I really mean any, crashes the phone in a rather spectacular way, heating up dramatically and progressively displaying scanlines until the screen is entirely white.
One exception : the fastboot flash command which doesn't work but displays the following -
Code:
D:\Android\platform-tools>fastboot flash bootloader bootloader-maguro-primela03.img
sending 'bootloader-maguro-primela03' (4760 KB)...
OKAY [ 0.456s]
writing 'bootloader-maguro-primela03'...
FAILED (status read failed (Too many links))
finished. total time: 0.551s
... after which the phone becomes dead an unresponsive like in my first post, and I have to defibrillate it with an OMAP flash, and so on and so forth.
So, the new status :
Harmless fastboot commands (like fastboot oem lock) crash the phone with much drama
Flash commands return "too many links" and kill the phone (OMAP Flash needed)
It's not a cable, driver, blah issue - I have another GNex phone here which I have flashed exactly the same way and all these commands worked fine.
This smells strongly of a hardware fault, so I'll be suggesting RMA tonight when I see my friend again (unless someone thinks of something else of course).
Thanks for all your help guys.

Same problem
I have the same problem here with my GNexus :/

I have the same problem with my Galaxy S1
I was flashing a new ROM on it, but Samsung Kies was running the background, process failed, (I closed Kies from task manager this time)
I tried to restart the phone in download mode but got the Phone-Triangle-PC icon.
Tried again to put the phone in download mode, then it went dead, unresponsive, absolutely silent, no lights...nara.
Let me try an OMAP flash -not sure how to yet...but google's a friend.

I got the similar situation with my GN, the phone boot into fastboot and odin mode but when I try to flash anything the screen goes black and start to show a white lines from top to bottom.
with mine I tried the OMAPFlash and it got stuck in this for hours
Code:
» Downloading complete
» Elapsed time: 0:01.445 (33680 bytes/s)
» End loading driver
» Downloading
» Downloading 'Targets\Projects\tuna\MLO_4460_HS_PRO'
» Sending data (131072 bytes) ::::::::::.......... [65536]
I hope you can find a solution to it.

I have a Nexus that is bricked too. It responds to OMAPFlash but nothing else, no fastboot or download mode. I'm going to try the USB jig today, otherwise I have to sell it.

Naezor said:
Last option before JTAG would be attempting an OMAP Flash. As long as it recognizes without a battery while plugged into the computer.
http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/
I use it all the time. I can fix about 4/5 bricks with this - if it doesn't, the processor is fried.
Good luck!
Click to expand...
Click to collapse
OMG!!!! THANK YOU for the link!!! I accidentally flashed a Nexus 7 Touch recovery on my GNex, and totally killed it. I was just about to post it on eBay as a "for parts only" auction! Thank you again!

Absolutely same situation
@AntoniusMaximus: What did you finally do?
I have a colleague's Nexus which was bootlooping. I tried to install from the factory image.
$ fastboot oem unlock
worked and the phone was unlocked.
$ fastboot flash bootloader bootloader-maguro-primelc03.img
gave the same error: FAILED (status read failed (Too many links))
and the phone could not see daylight again...the phone becomes dead an unresponsive.
I have not tried OMAP Flash. And have no clue as of now how to do that.
However, the battery does warm up when plugged to the charger.
Were you able to find a solution? The phone is just a couple of months old and can be replaced by samsung if i am able to lock it back (to have the warranty). Is there a way to do that?

Garfield. said:
@AntoniusMaximus: What did you finally do?
Were you able to find a solution? The phone is just a couple of months old and can be replaced by samsung if i am able to lock it back (to have the warranty). Is there a way to do that?
Click to expand...
Click to collapse
Sorry about that, I thought this thread was dead and buried.
The conclusion to this ordeal was fairly simple : RMA. This was apparently a NAND issue, one of these very rare hardware bricks. It wasn't caused by flashing, and it happened spontaneously while the phone was operating normally. No custom kernel, no overclocking.
It came to be as the very first device that I had to return, but thankfully I wasn't the culprit. I tend to be excessively cautions.
You can lock back the phone by putting it in Fastboot mode (phone -- triangle -- computer) and issuing the command :
Code:
# fastboot oem lock
Theoretically, unless they can find evidence that you overclocked anything, you should be fine.
Cheers,
Antonius Maximus.
--

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....

[Q][HELP] 16gb debrick image i747?

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.

S4 Mini Bricked?

My sister's S4 mini suddenly died, I cannot open the smartphone nor go on Recovery or download mode.
I used a debrick.img found here on xda put on a externaSD and manage to enter the download mode, then i try to flash a stock rom but it got stuck during the process (i leave odin running for hours without any success).
After that, when i retry the process this is what i got on screen:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
WRITE 139008 sectors. .
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
BOOTLOADER AP SWREV: 2
CSB-CONFIG-SLB: 0x30
WRITE PROTECTION: ENABLE
I try to flash different .pit file found here on xda for the i9195 but if i try to flash (using Odin 3.13 or even odin 1.85) it says
Re-Partition operation failed or There is no PIT partition.
Any other idea i can try?
Maybe another .pit file for i9195 and a firmware that work with it?
Thanks to everyone

Goku_ssj3 said:
My sister's S4 mini suddenly died, I cannot open the smartphone nor go on Recovery or download mode.
I used a debrick.img found here on xda put on a externaSD and manage to enter the download mode, then i try to flash a stock rom but it got stuck during the process (i leave odin running for hours without any success).
After that, when i retry the process this is what i got on screen:
I try to flash different .pit file found here on xda for the i9195 but if i try to flash (using Odin 3.13 or even odin 1.85) it says
Re-Partition operation failed or There is no PIT partition.
Any other idea i can try?
Maybe another .pit file for i9195 and a firmware that work with it?
Thanks to everyone
Click to expand...
Click to collapse
I think her EMMc chip is probably dead, so needs replacing (new motherboard)

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.