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.
--
Related
How to fix soft bricked galaxy nexus
I Bricked my Galaxy Nexus and there wasn´t anything i could do too fix it. But here is my fix and solution:
When you soft brick your phone you see only "phone -warning triangle- computer" when you power your phone. There is nothing to do, the phone wont be recognized in any platform or program then Odin.
In Odin with installed nexus galaxy driver in windows you can se that the phone is connected. But you cant flash it or do odin restore.
The solution:
On windows xp with installed nexus galaxy drivers.
1. Start Odin 3 v1.85
2. For PDA choose CF-Root-GGN_YAKJU_ICL53F-v5.1 (google and download it)
3. Power your Nexus Galaxy ( screen shows "phone- warning- computer") and connect it to you're PC.
4. START
Your Nexus Galaxy is back to track…..
PS: your phone whil boot whith dead android picture.. DONT do anything it whil reboot after 3-5 minutes by its self..
Fastest solution
Hard to believe that you lost fastboot mode on your phone. Did you try booting into fastboot mode (hold vol down/vol up then press power)?
Once in fastboot mode, just flash a stock image.
Re:
Think what you want. it was hard for me to believe that i was getting my expensive phone "soft bricked". You can´t get the phone in fastboot mode or any other.
By the way, thanks for instructions on how to put the phone in fastboot mode ...
the day you get a soft brick on your galaxy nexus, you will see that the only thing is to do as described above.
Sincerely, C : -
I got this screen too a while ago but it was a hardware issue so the motherboard got exchanged.
Please excuse me; I was only trying to understand. So putting the phone into fastboot mode resulted in the same "phone -warning triangle- computer" display?
I posted as I did because CF-Root-GGN_YAKJU_ICL53F-v5.1 is actually a rooted kernel from chainfire which flashes to the boot partition. In fact, that's what your Odin shot showed: "Firmware update start", followed by "boot.img". That indicated to me that your bootloader partition may have been still good since you can't boot without a valid bootloader partition. Fixing the kernel wouldn't have changed that. I was under the impression that fastboot itself is a bootloader partition function...
Also, this isn't a blanket fix since to avoid "soft bricking", LTE GNex owners should use CF-Root-GGN_MYSID_ICL53F-v5.1 instead.
For those of you who are interested in learning more about/obtaining these kernels for toro/maguro, go here.
tutorial or not ....
The only thing I know is that I tried everything .....
the only thing that helped was that what is stated.
What I want is to help others in my situation ...
Use at your own risk ..
I know that was what solved it for me ..
It's good to know if there are others who are helped in this way ..
Please write about it ...
Well, I don't know much about the Odin tool, and I'm still pretty much in learning mode on this device myself. I don't doubt that this technique fixed your soft brick error and I'm bookmarking this thread just in case it happens to me while playing with my AOSP environment, but I am intrigued by how....
Anything with odin makes me cringe.. takes me back to the days of my buggy s2.
Sent from my francoPhone
odin is da ****z
capanov said:
How to fix soft bricked galaxy nexus
I Bricked my Galaxy Nexus and there wasn´t anything i could do too fix it. But here is my fix and solution:
When you soft brick your phone you see only "phone -warning triangle- computer" when you power your phone. There is nothing to do, the phone wont be recognized in any platform or program then Odin.
In Odin with installed nexus galaxy driver in windows you can se that the phone is connected. But you cant flash it or do odin restore.
The solution:
On windows xp with installed nexus galaxy drivers.
1. Start Odin 3 v1.85
2. For PDA choose CF-Root-GGN_YAKJU_ICL53F-v5.1 (google and download it)
3. Power your Nexus Galaxy ( screen shows "phone- warning- computer") and connect it to you're PC.
4. START
Your Nexus Galaxy is back to track…..
PS: your phone whil boot whith dead android picture.. DONT do anything it whil reboot after 3-5 minutes by its self..
Fastest solution
Click to expand...
Click to collapse
hey dude it worked for me THANKZ THANKZZ THAKNZZZZ so muchhhhhh really appreciate your help, i will just install a new rom now can u advice a good rom for battery and customization please thnkz again to you and for all.
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Sleuth255 said:
Please excuse me; I was only trying to understand. So putting the phone into fastboot mode resulted in the same "phone -warning triangle- computer" display?
I posted as I did because CF-Root-GGN_YAKJU_ICL53F-v5.1 is actually a rooted kernel from chainfire which flashes to the boot partition. In fact, that's what your Odin shot showed: "Firmware update start", followed by "boot.img". That indicated to me that your bootloader partition may have been still good since you can't boot without a valid bootloader partition. Fixing the kernel wouldn't have changed that. I was under the impression that fastboot itself is a bootloader partition function...
Also, this isn't a blanket fix since to avoid "soft bricking", LTE GNex owners should use CF-Root-GGN_MYSID_ICL53F-v5.1 instead.
For those of you who are interested in learning more about/obtaining these kernels for toro/maguro, go here.
Click to expand...
Click to collapse
thaknz to you also buddy so much keep helping other God will help you first
There should also be an option in the command line version of heimdall to get rid of that screen and get the phone to boot normally. Don't know if it will work on the nexus but I know it worked when I had a Fascinate.
Sent from my Galaxy Nexus using XDA App
Interesting... this finally connects the dots for me as to what exactly a "soft brick" is. Thanks! I posted a writeup here
Re:
Sorry for the delay but had to work with my study .... doing "master of medical science" ...
Now back to the playground ... finally ..
Related to the SALYM's post:
I like the original yakju rom...
1. google and download image-yakju-icl53f.zip and unpack ( make sure it is zip file and not. tar)
2. google and download fastboot
3. use the fastboot commands .... tex in macos:
cd (path to the folder where you put all the files together)
./fastboot flash bootloader bootloader-maguro-primekk15.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-maguro-i9250xxkk6.img
./fastboot reboot-bootloader
sleep 5
./fastboot -w update image-yakju-icl53f.zip
That's all ...
PS i bricked my nexus again and succesufully got it fixed with my guide ... in just 5 seconds ....
Odin flashing, flashing stock images, bootloaders nothing work for my awkwardly bricked GSM nexus. If I try to flash a stock image, when I type in fastboot reboot-bootlader to reboot, my screen goes to a gray, gradient burnt looking image, then slowly fades to black and doesn't flash it at all. Using Odin, still stuck at pretty Google logo lol It's not really bricked per say, as I can get into fastboot mode, (no recovery without a million file doesn't exist errors, so no flashing roms or nandroids) but in fastboot mode, it won't take flashing stock images, bootloader.img, recovery.img nothin. When it tries, just gets the gray screen of death
HELP!! I have a VZW SGN unlocked and rooted running Axiom crossbreed rom today I kept getting this pop up saying I had a system update.. I kept clicking to remind me later because I know you cant do the update over a custom rom.. So Im in the middle of a text message and the screen goes black and my phone is now in a boot loop.. I tried to remedy this thru fastboot and in CWM reflashing the rom wiping data everything my last resort was Odin, which I tried but it hung at <ID:0/007> NAND Write Start!! after 10 or more minutes I removed usb and did a batt pull now I am only left with ONE screen and thats phone icon, yellow triangle with a ! in the middle and computer icon.. No matter what I do thats the ONLY screen I have.. So after MANY hours of research and reading I found this to try>
1. Start Odin 3 v1.85
2. For PDA choose CF-Root-GGN_YAKJU_ICL53F-v5.1 (google and download it)
3. Power your Nexus Galaxy ( screen shows "phone- warning- computer") and connect it to you're PC.
4. START
It acts like its doing something there a blue full line bar under the phone icon yellow triangle with the ! in the middle and computer icon now.. and on the Odin box where it should be GREEN and say PASS its GREEN but only says BOOT and this is what its saying below that> <ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!! < Once again hanging here.. Cant someone PLEASE for all the tea in China help me out b4 they have to sedate me and haul me off in a white jacket!!
Thanks :-(
Mendedlogic said:
[snip]
2. For PDA choose CF-Root-GGN_YAKJU_ICL53F-v5.1 (google and download it)
Click to expand...
Click to collapse
That is a GSM file, not a Verizon file. That's the first problem.
Sent from my Galaxy Nexus using Tapatalk 2
For Verizon cdma
Check the PDA line and put this file in it
"VzW-PDA-ODIN-I515EL03_ICL53F_signed"
Check the phone line and put this file in it
"VzW-PHONE-ODIN-SCH-I515.EK02_LTE"
You should be able to google up those files easily (since I don't have hosting space these days).
You need both of those files, 1 will not do and will bork you worse than you are now.
efrant said:
That is a GSM file, not a Verizon file. That's the first problem.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hmm weird that its the only file that acted like it was going to work too.. I wonder if there is a VZW version somewhere??
Mendedlogic said:
Hmm weird that its the only file that acted like it was going to work too.. I wonder if there is a VZW version somewhere??
Click to expand...
Click to collapse
I guess you're one of those people that have reading issues.....???
Look up.
n2ishun said:
For Verizon cdma
Check the PDA line and put this file in it
"VzW-PDA-ODIN-I515EL03_ICL53F_signed"
Check the phone line and put this file in it
"VzW-PHONE-ODIN-SCH-I515.EK02_LTE"
You should be able to google up those files easily (since I don't have hosting space these days).
You need both of those files, 1 will not do and will bork you worse than you are now.
Click to expand...
Click to collapse
I have both of those files and have been trying relentless to get it to work but Odin hangs at (NAND Write Stop!!) every time I know the bootloader img is in the pda but is there one maybe separate does anyone know was thinking if I can atleast try that too..
---------- Post added at 12:08 PM ---------- Previous post was at 12:03 PM ----------
n2ishun said:
I guess you're one of those people that have reading issues.....???
Look up.
Click to expand...
Click to collapse
Obviously Im not the one with reading issues, I was referring to the ROOT file.. Is there a reason for the rudeness really? Just trying to get my phone working again that's all
Hi,
I have a rooted Sprint SGS3 SPH-L710 which I was attempting to update from 4.1.1 to 4.1.2. I never did get the update to work and afterwards, I started getting random reboots, which seemed like SDS. Now powering it on puts it into a reboot cycle and it never gets past the Samsung Galaxy S III logo. Attempting to go into recovery mode gives the following kernel panic message:
Kernel Panic
KRAIT INFO
Panic caller : __stack_chk_fail+0x10/0x14
Panic Msg: stack-protector: Kernel stack is corrupted in: c002
Thread : swapper:1
Wait....
Done
Kernel Panic
Upload Mode
I can get into download mode, and have attempted to use Odin to flash both the kernel with KERNEL-SPR-L710VPBMD4-1366019975.tar and the ROM SPR-L710VPBMD4-20130418114128.zip which I obtained from samsung-updates.com
When I attempt to flash the kernel, I get the following from Odin:
Firmware update start…
boot.img
NAND Write Start!!
RQT_CLOSE !!
RES OK !!
Remain Port …. 0
All threads completed (succeed 1 / failed 0)
But no change in behavior on the phone.
When I attempt to flash the ROM, I get the following from Odin:
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection
Initialization..
Get PIT for mapping..
Firmware update start..
sbl2.mbin
NAND Write Start!!
FAIL! (Write)
All threads completed. (succeed 0 / failed1)
and I also get the following on the phone download mode screen:
ODIN : flash write failure
I've tried searching, but cannot seem to find much about the kernel panic. I'm guessing it is either a symptom of SDS or that I may have accidentally loaded an incompatible ROM when unrooting. I've tried flashing with Odin on different systems with different cables, but always get the same results.
tl;dr I have a soft bricked phone that gives a kernel panic error when I try to go into recovery mode and a write failure when flashing the ROM.
Any suggestions are appreciated.
Thanks!
I've never seen that before! Scary. Try using Odin with the files from this link, everything you need should be there.
http://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S3 (SPH-L710)/
Actually, use the tar file from this link
http://rwilco12.com/downloads.php?d...L710)/Stock ROMs/JB/MD4/Full Restore/Unrooted
Make sure you try different ports and cables when using Odin. Some things that helps me.
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Hit that "Thanks" Button if I helped you!
Thanks for the advice, Metalfan and Whiplashh. I have tried 3 difference cables and different usb ports. I also downloaded the file SPH-L710_MD4_1130792_Stock_Restore.tar.md5.gz that Metalfan linked, but got the same results from Odin as the other ROM I attempted loading.
I did notice something that changed before I attempted to load that ROM, the download mode screen now shows CUSTOM BINARY DOWNLOAD: No, it used to show 11. So I guess at some point in troubleshooting I must have reset the counter, but not sure that it really matters.
Now I'm condsidering trying this solution for hard bricked devices, I figure it can't hurt.
http://forum.xda-developers.com/showthread.php?t=2369125
I just thought I would post a follow-up to my own issue. All of my own attempts to flash a new ROM to the device were failing and the device was out of warranty, so I sent it off to a independent repair service who informed me the device had a bad eMMC (internal memory / memory controller) which I suppose matches up with the write fail errors that I was seeing. Not sure if I broke it while flashing it or if it was a result of the SDS symptoms that I had seen, either way its pretty much scrap now.
Hello readers,
It has been over a year since I've posted anything on these forums. I'll try keeping this post as short (yet as informative) as I possibly can. Chances are it won't be too short, but please take out some time and read this to see if you have a possible solution.
I recently bought my Samsung Galaxy T989D phone (a week ago) and updated it to 4.0.1 the day I did (I installed Kies on my computer). I then checked all around the internet for further updates and found that its clone, SGH-T989, was now able to be updated to 5.0.2. Wanting the update for my phone as well, I did an extensive research on this T989D, trying to figure out whether I can download the T989 updates on this. Every forum said yes, so I thought to give it a try. I wanted the latest version, but also only wanted to have it flashed from my phone, just so that I don't have to go through the rather long process of flashing it from the computer. I used this ROM: http://forum.xda-developers.com/galaxy-s2-tmobile/development/rom-aosp-lollipop-preview-t2931716
Stupidly enough, I did use the ROM but not the method for flashing it. All I did was merely install that file on my phone, reboot into recovery (I have TWRP; obtained it using ODIN v1.85), make the backup of ONLY my /data (was so sure it would flash without problem), Factory Reset, and flash the ROM...
After the ROM was installed, it rebooted itself - and that's about all it did. It was stuck on the Cyanogenmod 12 boot logo for a good 30 minutes before it chose to restart and repeat. Now it was just going on a boot loop. I then tried searching up a fix to this problem, but unfortunately, ALL of the websites that take you through the steps to unbricking your device require you to get into "Download Mode." I have access to only the TWRP Recovery mode, which doesn't have any "USB Debugging/Download mode". The closest it gets to is the "USB Storage mode". However, when I plug my phone onto the computer, the computer does detect it, and so does Odin. It says "Added!!" and the "COM:6" pops up. So then I thought that since it does detect my phone, it should work. And when I say "it" I mean this method of unbricking: http://forum.xda-developers.com/showthread.php?t=1513359
Instead of downloading the stock T989 ROM from Samsmobile.com, I downloaded the T989D ROM (4.0.1 was all that was available) and uploaded that to Odin v1.85. Now, it seemed to me that everything was going fine thus far- I got the right file; my phone is detected in Recovery Mode; and I had deleted everything prior to the flash. But once I press the Start button, these are the Messages that would pop up:
<ID:0/004> Added!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I would get this big "FAIL" sigh on the top. Other times in the message box I would get "All threads completed. (succeed 0 / failed 0)" Now the phone doesn't even show the Cyanogenmod 12 logo, set aside getting stuck there. After the "Samsung Galaxy S II T989D" page, the screen goes blank. So what's wrong here? Have I flashed wrong file(s)? Have I done something wrong in the process? Or is there another solution to this flashing problem? Some have said that the Odin application itself can be causing problems. Note that I have both Kies and Odin v1.85 installed on my computer, and (working)TWRP Recovery installed on my SGH-T989D phone.
Please don't mind the awfully long post - I'm trying to be as informative as possible to make it easy for anyone to point out any potential mistakes I've made during the process (or if someone has another possible solution to this problem). As of now I'm completely stuck, and not to mention fed up from searching so much and finding no fix to this problem. I would consider this phone my "prized possession" and would very highly appreciate anyone's help in this regard. Thanks in advance!
Kind regards,
Xx Jafours xX
UPDATE: I got my phone to work again. I did not use Odin v1.85; instead, I went ahead and installed another version of the T989D firmware. I installed it onto my computer, and then copied it onto my phone (I can do that through the TWRP's "Mount USB Storage" option.) And that was basically it - I just booted it and it worked! It did prompt me to install SuperSU. This ROM's current version is 4.0.2, but I'll be updating that through Kies. Luckily enough, I have my /data backed up in TWRP and will restore that once I update the firmware. Thanks for the moral support guys!
Xx Jafours xX said:
UPDATE: I got my phone to work again. I did not use Odin v1.85; instead, I went ahead and installed another version of the T989D firmware. I installed it onto my computer, and then copied it onto my phone (I can do that through the TWRP's "Mount USB Storage" option.) And that was basically it - I just booted it and it worked! It did prompt me to install SuperSU. This ROM's current version is 4.0.2, but I'll be updating that through Kies. Luckily enough, I have my /data backed up in TWRP and will restore that once I update the firmware. Thanks for the moral support guys!
Click to expand...
Click to collapse
Edit to add [SOLVED] to the title
Done. Thanks for the reminder.
Is anyone able to point me in the right direction or is willing to make one?
The i747 does not have a stock 5.1.1 rom; therefore, there is no debrick image for a 5.1.1 rom.
What bootloader is on the phone? Did any of the images from the debrick thread boot the phone?
Does installing 5.1 change your bootloader?
As in Cyanogenmod 12.1?
Softbricked my S3, and I'm not sure which way to attempt to recover/debrick & would appreciate any advice.
SGH I747 (ATT)
rooted 2 years ago just after 4.3 OTA updated, flashed with CM 11.
Had that on there for almost a year, got bored & installed carbonrom.
Beginning of december, flashed CM 12.1.
A week ago it got stuck on the boot logo.
Still able to get into both Recovery & download modes.
Clockwork mod 6.0.4.7
trying to flash from a new image or wipe & factory restore both give me
Code:
detected file system ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching unconditionally
E: error in /storage/sdcard1/cm-12.1-201511117-sna[status 0] installation aborted
trying to use Odin, it gives me
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
but never does anything, even hours later.
At unplug, I get
Code:
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The info on the download screen is
Code:
odin mode
product name: sgh-i747
custom binary download: yes (6 counts)
current binary: custom
system status: custom
qualcomm secureboot: enable
warranty bit: 1
bootloader ap swrev: 2
My guess from another thread is that the /system and /data partitions are not wiped properly, causing those partitions to be formatted with read-only (R/O) permissions rather than read-write (R/W)? But those files are definitely not right for my phone, so what now?
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
audit13 said:
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
Click to expand...
Click to collapse
Good to know.
Thanks.
But how do I get twrp onto the phone?
was actually trying to put twrp on with odin, but that's not working.
The downloads I've seen are for:
app-phone doesnt boot
odin- aint working
TWRP Install - Requires TWRP 2.8.4 or higher already installed
dd Install Method - oh, didn't see that one. I'll try that & let you know.:laugh:
---------- Post added at 06:54 AM ---------- Previous post was at 06:16 AM ----------
well, I'm not figuring it out....
As per the twrp page, tried: dd if=/sdcard/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
tried: dd if=/storage/sdcard1/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
did ls (hey it's like linux!)
got possible locations: external_sd, sd-ext, sdcard, also looked under mnt.
file not found error
cd'ed & ls'ed to /storage/sdcard1/ there it frickken is!
ran the command there, sans path, and still get file not found error
arrrrgh.
Try this:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy
very detailed response, thanks. I've tried most of that, as some thread I was reading said that twrp probably has the capability to fix the issue, and CWM definitely doesn't.
Odin never really does anything, though. How long should I wait?
This step is the one I haven't done "7) open Odin 3.07 and uncheck everything except f. reset time;" Just left everything alone the multiple times I tried. Hopefully that'll make a difference.
Tried 3.07, 3.09, 3.10.6. I'll try again.
By default in Odin 3.07, only auto reboot and f reset time are checked.
What do you mean when you say Odin does nothing? Does the phone appear as a com device in Odin? Are there error messages in Odin during the flash process?
never gives anything other than:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
not at a windows computer for a couple days. stuck on linux mint with no internet. has heimdall & adb, though....
have twrp img & tar, cm12.1, and gapps on the sdcard.
All I can suggest is to try and get access to a pc or try VMware with win7.
Tried again last night for about 12 hours, no response from Odin.
Decided to give jtag a shot.
Contacted the jtag guy & gave him all the above info.
He says
"Unfortunately there are many indicators that your phone has a hardware failure.... Most likely a failed emmc memory chip.
1) the phone getting stuck on boot logo for no reason.
2) Odin not flashing...
3) files not found or... Not being able to do.
These are all indicators that the emmc memory chip is toast...... The biggest clue is finding the phone stuck on boot logo... Out of nowhere for no reason.
Jtag would not be able to fix it.
Thank you"
:crying::crying::crying::crying::crying::crying:
Thanks for the help.
Might sell the remains.
16G I747 blue, normal wear & tear, small chip in one corner, the case covers it.
2 stock batteries
1 7800mah best4power battery
1 otterbox defender modified to hold extended battery without the turtleback
any offers?
i suggest trying on a Windows machine before giving up. I am not convinced the memory is damaged.
That was on a windows machine...
Odin recognizes the phone but it won't flash twrp? Have you tried different USB cables and USB ports?
I found that my s4 and s3 would fail to flash if I don't use the USB cable that came with my Samsung or LG phones.
yes to both cable & ports.
bought an LG K7, which I mostly hate, and can not root.
keeping my S3, looking for someplace cheap to replace the chip.
I bought my lg k7 today(LGMS330)metropcs i rooted it in 2 mins.with xda's KINGROOT..then removed Kingroot with WOLFDROIDS script...and now im running BUSYBOX STERICSON 1.24.1 and ChainFires SUPERSU 2.49..IT KILLS me when people cant root there devices...i did this ALL in the BURGERKING BATHROOM GOIN BOO BOO
Ok so i rooted my darn k7 ...but like a jackars i bricked it...no TWRP...NO KDZ FIRMWARE...CAN ANYONE PLEASE ...PRETTY PLEASE SEND ME A LINK TO THE METROPCS variant of the LG K7 (TRIBUTE 5) KDZ STOCK FIRMWARE..I JUST BOUGHT A $150 ELECTRONIC PAPERWEIGHT...the k7 is so new there is no support anywhere...in fact all u really find is the ads for the debut of the device in stores ...major noob mistake..im truly embarassed..PLZ HELP
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
just got a $150 paperweight...lg ms330 i do hate you now...
o4tuna said:
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
Click to expand...
Click to collapse
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
AbErCrMbPlAyA said:
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
Click to expand...
Click to collapse
I had a amazing talk with the lg develeopers yesterday....since I am in the same boat since my lg k7 is bricked....I ask them for the kdz firmware so I can reflash my phone....you wanna know what they told me?
first they ask: whats a kdz file?
their answer: We don't make those thing you need the official lg tools to update your device firmware....so we cant help you...
Me: I am extremely pissed now since they are lying to me & then I showed them a link from their server to DOWNLOAD a kdz file firmware for another device that I had....
their answer: we dont know what you are talking about...sorry we can't help you!
I even went to my nearby metropcs store & explained to him what happen...
first. he didn't understand the following:
1-bootloader
2. boot image
3. recovery mode
4. download mode
5. kdz firmware
6. bricked & softed-bricked
the f-cking guy told me I can't do anything, but "report my phone lost or stolen" so I can get a new one....
How the hell are these idiots getting jobs when they have NO IDEA what to do on how to fix a phone
My level of anger is now over 9000.....
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.