I was performing a nandroid backup when then the progress line stopped. I let it sit for over 4 hours and the line did not move. The phone was locked up. I took the battery out to reset the phone and now it will not turn on. I tired several different key comobs, including volume up+down and power, with no efffect. When I plug it in it does nothing. I was using ISCrewD with the Siyah kernal now for a couples months with no issues. That was actually the only custom rom I ever flashed to the phone, loved the rom. From reading the forums, it seems I am hard bricked. How did that happen? Any suggestions?
Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones.
Version 2.6.13.
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
votinh said:
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
Click to expand...
Click to collapse
no, it's for GB, just checked G's site. However, there are 4 download entries, one of which is the Korean based (possible bricker). What's more, G could've rebased the ATT version from the Korean... I'd be amazed if, after all the bricking going on, he'd still have a download for it. Weird.
Galaxy_Cat said:
no, it's for GB, just checked G's site. However, there are 4 download entries, one of which is the Korean based (possible bricker). What's more, G could've rebased the ATT version from the Korean... I'd be amazed if, after all the bricking going on, he'd still have a download for it. Weird.
Click to expand...
Click to collapse
For real? Siyah 3.1.rc6 is for GB?
You were doing a nandroid backup, not a restore, and on gingerbread, so it's hard to say what caused the problem. I don't believe I've seen any report exactly like yours.
You tried several button combinations, including recovery mode, which did not work, but did you try to get into download mode? First try to enter download mode with the battery in -- hold vol+ and vol- (but not pwr) and then plug in the usb cable. If no success with that, pull the battery and do the exact same sequence to enter download mode. The usb cable will provide the power. Sometimes there is a problem with the battery. If you can get download mode, you're not bricked.
votinh said:
For real? Siyah 3.1.rc6 is for GB?
Click to expand...
Click to collapse
what are you talking about? Read OP response.
votinh said:
OP, you must have done something weird (or power loss) during the backup as there is no way nandroid backup in CwM causing hardbricking.
jojo, that version of Siyah was for ICS, the OP ran GB.
Click to expand...
Click to collapse
My bad. I've only had this phone for a week and never used that ROM...just assumed it was ICS based on the name.
Galaxy_Cat said:
what are you talking about? Read OP response.
Click to expand...
Click to collapse
People on the net are freaking confusing me.
What the heck you are talking about? OP response of what?
Were you misquote/misread/misunderstand what I said?
I said to member "jojo" above when he mentioned the Siyah 3.1rc6.
Are we in the same page? I guess not.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Here's what jojo said: "Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones."
ENTER
ENTER
ENTER
And that was my response to him.
Were you the dude misread my post earlier???
votinh said:
People on the net are freaking confusing me.
What the heck you are talking about? OP response of what?
Were you misquote/misread/misunderstand what I said?
I said to member "jojo" above when he mentioned the Siyah 3.1rc6.
Are we in the same page? I guess not.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Here's what jojo said: "Do you remember what version of Siyah you were using? I read recently that 3.1RC6 had a major bug in it that was hard bricking people's phones."
ENTER
ENTER
ENTER
And that was my response to him.
Were you the dude misread my post earlier???
Click to expand...
Click to collapse
I misread you (had to reread this thread three times to get it straight!) sorry for confusion.
It is a GB rom/kernal...
I tried, as said above, to hold down vol up and down, then insert the usb cable, no go with or without the battery in. My wife has the same phone, so I tried her battery and no go, then put my battery in hers and all was fine. So battery seems ok. I have played around a good bit with it this evening, and read a good bit in the forums...all points to hard bricked. I have no idea how it happened, I have seen no others (at least from my seraches) have this problem with nandroid backup. For that matter I have used it before with this rom/kernal and no issue. Warranty is still good on it, guess I will try and get it exchanged, hopefully they don't get it to boot up with a custom rom on it. No way for me to restore it back to stock of course.
gandalf21502 said:
It is a GB rom/kernal...
I tried, as said above, to hold down vol up and down, then insert the usb cable, no go with or without the battery in. My wife has the same phone, so I tried her battery and no go, then put my battery in hers and all was fine. So battery seems ok. I have played around a good bit with it this evening, and read a good bit in the forums...all points to hard bricked. I have no idea how it happened, I have seen no others (at least from my seraches) have this problem with nandroid backup. For that matter I have used it before with this rom/kernal and no issue. Warranty is still good on it, guess I will try and get it exchanged, hopefully they don't get it to boot up with a custom rom on it. No way for me to restore it back to stock of course.
Click to expand...
Click to collapse
You need the USB dongle to force it to
Go in download mode.
Sent from my GT-N7000 using XDA
From what I have read, that will only work if you get 'some' response when turning it on. I get nothing, so the dongle will not work?
I called AT&T this morning, I can get a refurbished one to replace mine, guess I will go that route....
gandalf21502 said:
From what I have read, that will only work if you get 'some' response when turning it on. I get nothing, so the dongle will not work?
Click to expand...
Click to collapse
So just because it might not work, you're not going to try it? Try it!
Well...why not! I found one on Ebay for under $10 shipped, so it's on the way...
gandalf21502 said:
Well...why not! I found one on Ebay for under $10 shipped, so it's on the way...
Click to expand...
Click to collapse
Just to be clear, when we say USB dongle, we're not taking about a USB jig...we're talking about the USB-to-MicroUSB data cable that came with the phone.
I have already tried the micro usb cable that came with the phone and tried to get Odin to see the phone, no go. I ordered a Jig to see if it would force the phone into download mode...
Got my USB Jig today. Took the battery out (even tried wifes 'good' battery). Put the battery in, then the Jig...nothing. I would assume the phone has some form of hardware failure...guess time to get ahold of AT&T and get a warranty exchange.
AT&T is sending a 'refurb' phone today...should be here soon...hopefully they don't get my phone to work and see the custom kernal/rom...No matter what I try, it just won't come on.
Related
I've seen a section on how to use the jig device but I don't think its going to work. Heres the thing, my phone is completely dead, no "Vibrant" screen, no download in anyway possible, no charging screen. Is there hope? Please help me :'(
This happened to me once, I could not get it to respond in anyway what so ever.... after being pissed and leaving it alone for about 20 minutes I came back and tried this...
1. Open your phone and take our your sim card, battery and external sd if you have one
2. Plug in your usb cord
3. Hold volume up and down, DO NOT HOLD POWER only volume buttons
4. Place battery back in phone and watch for the screen to respond
5. Release Volume up and down buttons
This method got me in to download mode even though I tried it like 100 times, it was only until after I let me phone sit for a little bit did it respond. Even if you have already tried this.... try it again. I went thru the same thing.
Solissfiend said:
This happened to me once, I could not get it to respond in anyway what so ever.... after being pissed and leaving it alone for about 20 minutes I came back and tried this...
1. Open your phone and take our your sim card, battery and external sd if you have one
2. Plug in your usb cord
3. Hold volume up and down, DO NOT HOLD POWER only volume buttons
4. Place battery back in phone and watch for the screen to respond
5. Release Volume up and down buttons
This method got me in to download mode even though I tried it like 100 times, it was only until after I let me phone sit for a little bit did it respond. Even if you have already tried this.... try it again. I went thru the same thing.
Click to expand...
Click to collapse
I've tried that but I'll let the phone rest for awhile. It happened when I was updating to 2.2 from 2.1 using Kies, I wasn't rooted or anything and I had just formatted the phone prior to that.
Burner2K0 said:
I've tried that but I'll let the phone rest for awhile. It happened when I was updating to 2.2 from 2.1 using Kies, I wasn't rooted or anything and I had just formatted the phone prior to that.
Click to expand...
Click to collapse
Same thing happened to me. Did everything as written above. Nothing seemed to work. Then....I put the battery in, left it overnight to charge. Tried it all over again and... IT WORKED!!!!
Sent from my SGH-T959 using xda premium
Nthe jig woulda worked for all of you
Sent from a cell tower to the XDA server to you.
Please post these in the right section...
This being said just hold the volume up button and plug in the usb cord this should force download mode.
How to make a jig
Or Buy One Here
toryheal said:
Please post these in the right section...
This being said just hold the volume up button and plug in the usb cord this should force download mode.
How to make a jig
Or Buy One Here
Click to expand...
Click to collapse
Isn't this posted in the right section? I mean,it does regard flashing and using Odin...
toryheal said:
Please post these in the right section...
This being said just hold the volume up button and plug in the usb cord this should force download mode.
How to make a jig
Or Buy One Here
Click to expand...
Click to collapse
And no, holding vol-up and plugging in usb does nothing.
Burner2K0 said:
Isn't this posted in the right section? I mean,it does regard flashing and using Odin...
Click to expand...
Click to collapse
This is a question trying to be answered (so Q&A is proper place) this is a section for devs to post and support their work. this wasn't to flame rather to let one know
---------- Post added at 08:32 AM ---------- Previous post was at 08:30 AM ----------
Burner2K0 said:
And no, holding vol-up and plugging in usb does nothing.
Click to expand...
Click to collapse
Well then i suggest trying the one where you pull out the battery and try it that way or get down and dirty and make a jig or purchase one from the link i sent you.
toryheal said:
This is a question trying to be answered (so Q&A is proper place) this is a section for devs to post and support their work. this wasn't to flame rather to let one know
---------- Post added at 08:32 AM ---------- Previous post was at 08:30 AM ----------
Well then i suggest trying the one where you pull out the battery and try it that way or get down and dirty and make a jig or purchase one from the link i sent you.
Click to expand...
Click to collapse
None of the steps work. My best bet is to buy a jig, but if phone is fully bricked, will that even work at all?
Burner2K0 said:
None of the steps work. My best bet is to buy a jig, but if phone is fully bricked, will that even work at all?
Click to expand...
Click to collapse
brother it is a game of chance either you take a ten dollar lose or you take a 130 dollar lose choice is yours but the have been a many of times where the jig has saved my ass...
toryheal said:
brother it is a game of chance either you take a ten dollar lose or you take a 130 dollar lose choice is yours but the have been a many of times where the jig has saved my ass...
Click to expand...
Click to collapse
Lets just hope it works, first have to put money in my paypal account. Kind of ironic how I've flashing ROMs here and there for a good while and the day I decided to go from stock 2.1 to 2.2 using Kies, it bricks >_>
Burner2K0 said:
Lets just hope it works, first have to put money in my paypal account. Kind of ironic how I've flashing ROMs here and there for a good while and the day I decided to go from stock 2.1 to 2.2 using Kies, it bricks >_>
Click to expand...
Click to collapse
Yeah i am guessing kies may be the issue. I would suggest giving it a try and if that doesnt work mobiletech jtags now
You can contact connexion2005 he is the best.
sadly.. for every 1 post I read about someone bricking a phone while flashing custom ROM, I read 4 or 5 of people bricking w/Kies..
did you ever have any 2.3.x roms on your phone? bootloaders?
"Kies ate my phone" is still an excellent way to get a new phone regardless of the current warranty.
G1toVibrant said:
sadly.. for every 1 post I read about someone bricking a phone while flashing custom ROM, I read 4 or 5 of people bricking w/Kies..
did you ever have any 2.3.x roms on your phone? bootloaders?
Click to expand...
Click to collapse
Yes I have, I had GB bootloaders on the phone but never switched them back to Froyos BL even when I flashed 2.2 ROMS, could that have been the problem?
Burner2K0 said:
Yes I have, I had GB bootloaders on the phone but never switched them back to Froyos BL even when I flashed 2.2 ROMS, could that have been the problem?
Click to expand...
Click to collapse
I know that you said you tried odin.... have you tried the One Click unbrick by Adam O and company? Sorry... that is heimdall to most... you can set it to load boot loaders for you, maybe this can help?
Hard Brick with Kies
Just wanted to say i did the same thing when i got my vibrant, i had busy box which i think was the reason kies failed on me.... but i called Samsung and they didn't even think twice about claiming warranty. They re flashed 2.2, and i bough the phone used of eBay, give them a shot.
cmzeunges said:
I know that you said you tried odin.... have you tried the One Click unbrick by Adam O and company? Sorry... that is heimdall to most... you can set it to load boot loaders for you, maybe this can help?
Click to expand...
Click to collapse
Judging by the thread, I doubt its going to work. It needs to atleast boot, which is what my phone isn't doing. Basically it acts as if there is no battery in, doesnt boot, no download mode, no charging screen. Computer wont pick it up either.
call me a noob, but i thought that Odin was taking too long (45 mins)(tried to switch from CM7 to stock firmware) and was stuck, so i closed out and turned off my phone by taking out the battery (idiot, i know) and now my phone wont turn on, and ive tried taking out the battery, pressing a number of button combos, and the people at radioshack didnt help (big suprise). any ideas?
Try holding the power button alone, for like 15 or more seconds.
Not sure beyond that....
didnt help...what i think the problem is that i dont have a firmware on my phone to boot it from...
You need enter download mode. It's not clear from your post if you tried to enter download mode or not. Can you get into download mode? Do you have a jig?
Btw, 45 minutes was definitely too long for Odin, so there probably wasn't any thing else you could have done.
no, i cannot get into download mode, and i do not have a jig. would that fix the problem completely?
Unsure - seems like somehow you killed your bootloader, not sure how since no return-to-stock package has bootloaders.
You should be able to get into download mode by this method: With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button). When the warning screen appears, press Volume up to continue into download mode.
The jig is just another way to get into download mode, and certainly worth a try if you have one or can borrow one. With the phone powered off, plug in the jig, and the phone will immediately go into download mode.
You must have enough charge on the battery for the phone to turn on.
If the battery has charge, and you are unable to get into download mode by any method, and if you are unable to get any signs of life from your phone in any way, then as Entropy said, you may have damaged bootloaders.
The only way to damage one of the bootloaders, as far as I know, is for Odin to be interrupted while it is flashing the bootloader. So this begs the question, what exactly were you trying to flash that didn't complete in 45 minutes?
If your phone is truely hard bricked, the only way to recover it is to send it to a professional like connexion2005 of Mobile Tech Videos who can use jtag to reset the bootloaders.
Oh oh, I feel bad for the OP.
People keep saying this device is "unbrickable" but apparently not.
votinh said:
Oh oh, I feel bad for the OP.
People keep saying this device is "unbrickable" but apparently not.
Click to expand...
Click to collapse
He should be able to clear it with a jig, but no one can guarantee that this will work. I have seen it fix this issue before though.
votinh said:
Oh oh, I feel bad for the OP.
People keep saying this device is "unbrickable" but apparently not.
Click to expand...
Click to collapse
No one claims it's unbrickable - just that it's damned hard to brick.
I'm still curious what he was trying to flash - I have NEVER heard of anyone hardbricking their devices unless:
1) They screwed with bootloaders - which is why I have included gigantic red warnings with anything I post that includes a bootloader
2) They flashed something not intended for the device
Iskor12 said:
He should be able to clear it with a jig, but no one can guarantee that this will work. I have seen it fix this issue before though.
Click to expand...
Click to collapse
If the bootloader somehow got corrupted (like crawly and Entrophy mentioned) then a jig won't do any good, I think.
It's good that some guru can access and reprogram the bootloader via JTAG.
I keep fingers crossed for OP.
---------- Post added at 09:54 PM ---------- Previous post was at 09:44 PM ----------
Entropy512 said:
No one claims it's unbrickable - just that it's damned hard to brick.
I'm still curious what he was trying to flash - I have NEVER heard of anyone hardbricking their devices unless:
1) They screwed with bootloaders - which is why I have included gigantic red warnings with anything I post that includes a bootloader
2) They flashed something not intended for the device
Click to expand...
Click to collapse
Experienced people can avoid those fundamental mistakes but newbies often get hair pulling, head scratching before mumbling "dang, why would I do that in first place"
Entropy512 said:
No one claims it's unbrickable - just that it's damned hard to brick.
I'm still curious what he was trying to flash - I have NEVER heard of anyone hardbricking their devices unless:
1) They screwed with bootloaders - which is why I have included gigantic red warnings with anything I post that includes a bootloader
2) They flashed something not intended for the device
Click to expand...
Click to collapse
Personal experience here. Flashed a one click for a captivate and bricked it a year ago. Went through everything, reported a success, and even sent reboot command to phone when it was done. 'Rebooted' to a black screen. For the better part of a week I tried everything, and I mean everything. Just unbricked last night/this morning with the 'unbrickable mod'. Wow micro soldering.
What led up to this was flashing a friends captivate with another one click odin package. Bricked it too (really need to quit doing that) but I think a usb jig might have worked on that one, but didn't have one with me. After doing the unbrickable mod to the phone that sat for over a year, I flashed it with the same package that just bricked the second captivate, and it worked fine. I did nothing different. I'm very patient in doing things the right way. Same steps, same software, same computer, no brick.
Sent from my páhhōniē
To the OP
Is getting Samsung Tech support an option, if everything else fails, then you dont have anything to lose, they support by phone and was pleseantly suprised with their help.
AdamOutler is willing to work on bringing the unbrickable mod to the i777. All he needs is an i777, bricked or not. If anyone has one that is bricked, by all means send it to him. He said not only will he
unbrick it using jtag, he'll attempt to do the unbrickable mod to it.
I'd be willing to donate to him and anybody who helps make it possible by sending him their phone.
Sent from my páhhōniē
OK so I did the HTCDev unlock perfectly fine, then flashed the Leedroid rom (using cwm) and the kernel (using fastboot), it loaded up and was working great until I made a phone call! Within about 2 minutes of the call it cut out completely (had about 70-75% battery), and I mean it literally just completely shut off and now it won't turn back on. I have done battery pulls, tried a different battery, plugging into charger (but light doesn't even come on!). What is going on?
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
fpineda101 said:
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Atomix86 said:
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Click to expand...
Click to collapse
Weird... Have u tried vol down+power?
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
wikdNoob said:
Weird... Have u tried vol down+power?
Click to expand...
Click to collapse
Yes it was one of the first things I tried.
ycats said:
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
Click to expand...
Click to collapse
I wish I could do that but I can't boot using any button combination at all
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
ycats said:
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
Click to expand...
Click to collapse
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
ycats said:
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
Click to expand...
Click to collapse
Yes I tried placing the file on the memory card, no dice. And no I don't get a red light when plugging into charger. It's as if the ROM or whatever the issue is, has completely destroyed it.
Atomix86 said:
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
Click to expand...
Click to collapse
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
tgruendler said:
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
Click to expand...
Click to collapse
Used it for about an hour as stock, but that is irrelevant. I wasn't "screwing around" either, I have flashed many phones in my time and always follow the guides provided to completion. The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Atomix86 said:
The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Click to expand...
Click to collapse
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Did you change the max CPU? What about undervolting?
tgruendler said:
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Click to expand...
Click to collapse
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Atomix86 said:
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Click to expand...
Click to collapse
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Yep... sounds to me like a hardware failure. Shiat! :-/
tgruendler said:
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
Click to expand...
Click to collapse
That is very true, I was just hoping that the kernel "boot up" so to speak could be avoided by opening fastboot and flashing a stock rom back. But as you stated perhaps the undervolting has messed something up. Thank you very much for your insight and help.
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Funnily enough this is what i'm going to do now, having a quick google search shows a few people suggesting to do this (im not quite sure what it does, something to do with the phone dispersing the charge it has inside it or some such?), so thanks for the suggestion!
Jakedude2011 said:
Yep... sounds to me like a hardware failure. Shiat! :-/
Click to expand...
Click to collapse
Indeed
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Holy crap, this actually worked! Now I just have to find a way of removing that nasty kernel xD
AWESOME! I believe the stock kernel would be in that .zip file if it flashed from recovery.
-----------------
---This first post is outdated. My current question is one post below. I've left the content of this post for other noobs to see.
-----------------
Hey folks, sorry to bother you all but all input would be greatly appreciated. I'm rather unfamiliar with android flashing and kernels, and have spent the last 8 hours trying to figure this out to no avail.
Following this (http://forum.xda-developers.com/showthread.php?t=1238070) (section 5) guide on how to get back to stock gingerbread on my phone (after a few partially failed attempts flashing other roms), I was using Odin, had the .pit 2.2 as well as CI500_VZW_EH03_GB_CM.tar.md5 loaded into the program and left it running. About 20 mins in, the phone stopped progressing and I started to get concerned. After two hours, I powered down the phone and proceeded to reattempt the flash. This is when things got weird. My phone was unable to enter the Download Mode and instead showed Android system recovery when plugged in, or a black screen with a phone and a computer, with arrows between when not plugged in. The weirdest part is that the phone no longer recognized vol+ or the power button when in Android Recovery, and could only vol- to go down the menu, then was stuck at the bottom of the list.
I've searched everywhere on this site, and google to try and come up with a solution.
When pluggin into the computer, I hear a connection sound, but the device is not recognized by Odin. Pressing the running a blind vol+ and vol-, then a vol- to hope Odin recognizes the device, as pointed out in this (http://forum.xda-developers.com/showthread.php?t=1764022) thread, resulted in nothing. Holding vol- while pluggin in the usb cable, doesn't show the download mode. All of the steps in this (http://forum.xda-developers.com/showthread.php?t=1026746) thread proved futile, as most of them required download mode anyways.
I'm going to keep searching and keep you posted as things come. Your help as always will be greatly appreciated!
Edit: Things just got weirder... After a few more attempts at making this work, I'm now getting an "Unable to charge non-supported battery. See user manual." With this error, I'm not able to get into Android Recovery anymore. More searching...
Edit 2: AFAIK I'm gonna need a jig. Anyone confirm?
Edit 3: Got a jig, Download Mode working, all is well. Please remove this thread, or leave it for other noob flashers to see.
Hey Folks, its been a while since I last posted in this forum, but I ran into a pretty serious issue earlier this evening. I was attempting to flash CM9 to my T959D and was running into tonnes of trouble. Throughout my attempts I was restoring back to stock rom, kernel and bootloader. During one of these restores, Odin froze in Win 7. Since then I've been unable to detect any form of life from the phone. It simply sits in a black screen. Holding the vol down while booting, blind vol up and down cable inserting, using my Jig and inserting the cable/battery in various orders results in nothing. The most I hear is a device failure to connect sound in Windows with no sign of life in Odin.
What can I do?
Someone posted stating leaving the battery out for multiple days would reset something on the motherboard, allowing me to get into download mode. Though I was hoping to have this resolved tonight. I realize that there aren't many people left with these phones, but I hope someone has a solution to this.
I'm going to be installing ubuntu tonight on an older desktop in a effort to resolve this. Though my experience with it is very limited, and success is unknown.
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
NOT GOOD... You should wait and see if others have a better solution, but Unbrickable Mod may be your only option.
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
TheMegosh said:
Thats not good to hear. Well, I was snooping around looking for someone who could solder this for me, to no avail. My soldering skills are non existent. The most I fixed was a door bell, and I did a terrible job. I won't be able to get my hands on a soldering iron until tomorrow, is it worth trying?
I have located someone who can do a jtag on this model but have a few questions in regards to this:
Since my bootloader was corrupted, would the jtag service put a new bootloader on?
Would it prevent the same thing from happening again?
Are jtags designed on a per-phone basis?
Since there is a telus fascinate T959D as well as a verizon fascinate, and both phones are completely different, would I need to make sure the jtag is meant for this phone?
Is there anything I need to be made aware of before doing this that I haven't mentioned?
Click to expand...
Click to collapse
Make sure you use the stock Samsung cable see if you can reinstall the drivers hook it into the computer and hold volume down if you can get any type of signal from the phone your good.
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
MultipleMonomials said:
I've haven't had any experience with JTAG, but I've heard Unbrickable Mod is preferable. If you're looking for someone who can solder, check out your local RC/hobby store. If that fails, check out an electronics store, though it may take some searching to find one.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Hey no offence but stop telling everyone on the street they need too soljeir there phone with unbrickable mod before they can fix I'm tired of having too calm the person down after you said they have too open up the phone its utter bull****. 1 out of 10 soft bricks you may need it I've been without download mode and fixed mine just fine.
Sent from my SCH-I500 using Tapatalk 2
An update:
Took my phone in to get the jtag service... He said some of my partitions were corrupted, one of which was the boot layer. He put a new bootloader on, and showed it could be placed back into recovery and download mode, but when I got home the device was even more dead than when I left; no device failed to connect sound in windows, just nothing. I'm taking it back to him in a week after exams to get this resolved. Maybe the battery has reached the end of its life...? I checked it with a volt meter, and it had 3v+ so I really don't know.
Sent using Science!
As bbrad pointed out, there may be other solutions, and my answer could be totally wrong, but if even your bootloader is cooked, Unbrickable Mod may be your only hope. Since UM affects startup code literally hardwired into the chip, it should work as long as the JTAG doesn't interfere.
Posted from my Fascinate using XDA Premium
Another update. So apparently I flashed a bootloader from another phone, which royally screwed up the partition, kernel and mounted drives. The technician managed to get the original bootloader, kernel and rom on the phone and everything is working from stock again.
Why on earth is the 959d Telus version such a pain in the ass to customize?
Is there anyone on here that uses a 959d that can direct me to a proper method to leaving stock? Before this entire situation I had vodoo kernel on, with cwm, but every time I flashed a kernel it would hang on reboot and either sit on a black or white screen. In a lot of cases I would flash in cwm, reboot, then I would be brought back to cwm as if there was no rom on the phone at all, no matter what I formatted and wiped.
When I'm not on my phone I can link all of the guides I've tried that leave me back where I started. So I re flash back to stock using Odin.
At the end of the day, I have to ask, is it really worth it in the end? I've rooted and flashed many roms on other phones but have never run into as many problems as with this fascinate t959d
Sent using Science!
Hello everybody.
I was using the first "official" JB leak (the Polish one, I don't remember which one it was). I've being used it for a while, with no problems.
Yesterday, I saw that Faryabb had posted a new version of the GAPPs. Since I wanted the "pinch to zoom" thing in Gmail, I did the following:
- Installed ROM Manager
- Installed CWM from ROM Manager
- Installed CWM Touch on top of that using ROM Manager
- Flashed the GAPPs using CWM.
The phone booted and did it "Updating 37 of 216 apps" or something like that. Everything seemed fine ('though I was mistaken, this version of Gmail didn't have pinch to zoom either).
Anyway, this morning I reached for my phone and it's off. It won't turn off even after pressing any combination of VolUp+Home+Power or VolDown+Home+Power.
I've tried pulling the battery, waiting for a couple of minutes and putting it in again, with no luck.
I'm starting to get "a little bit" worried. Does anybody have any idea of what may have happened?
Thanks in advance.
Edit: When I plug in the phone, the LED does nothing. It doesn't turn on at all.
Try find another battery and test it. If still no response, send back to service centre.
Sent from my GT-I9300 using xda app-developers app
f first thing,, make sure battery is charged, sounds stupid, but it happens
Try using usb jig..it might work...
and yeah charge battery just in case..
Thanks for all your answers.
Battery was at 50% when I went to bed. And it doesn't charge when I plug in the phone.
Anyway, I'll try to buy a new battery and see if it works.
I don't own an USB JIG. However, having read about it, it seems that it won't help with a hard brick (like the one I seem to have).
"bit worried"
reycat said:
Thanks for all your answers.
Battery was at 50% when I went to bed. And it doesn't charge when I plug in the phone.
Anyway, I'll try to buy a new battery and see if it works.
I don't own an USB JIG. However, having read about it, it seems that it won't help with a hard brick (like the one I seem to have).
Click to expand...
Click to collapse
Hi All,
I have the same problem. I am using Omega 27.2 and latest syiah kernel. I tried to dual boot with rom supernexus. Everything was fine when I went to bed. But in the morning I was not able to switch the phone on. I tried new battery, nothing. I tried to charge both batteries, nothing. I tried to press buttons for download mode, nothing. Iam really worried about it now. Please help.
Friend have USB JIG so I will try it tomorrow and let you know. But still if you have anything else, let us know.
Thank y ou
one last ditch attempt before the jig
Make sure your phone is charged
Try long press power button (10 second+)
That's all I can think of right now
Thanks again.
Since it seems that the phone isn't charging the battery, I've just bought an Extra Battery Kit + Charger and I'm charging the extra battery with the charger. When it has a full charge I will put that battery in and try everything you've recommended.
USB Jig will only enable the phone to boot to download mode if the buttons dont work .
As its small cost always worth a try with no warranty phones .
My guess ROM Manager is the problem
CWM
Not compatible with ROM Manager ! Use the CWM Manager provided instead (installed by CF-Root automatically)
jje
Well spotted jj, I missed that he had used Rom manager
reycat said:
Thanks again.
Since it seems that the phone isn't charging the battery, I've just bought an Extra Battery Kit + Charger and I'm charging the extra battery with the charger. When it has a full charge I will put that battery in and try everything you've recommended.
Click to expand...
Click to collapse
@reycat
Try it, but I have changed battery for the reserved one which was fully charged and nothing happend.
@all
any other tips to bring our phones back to life?
I have backup, but I can not do anything with it because I can not switch on the phone (
Thank you
---------- Post added at 10:59 AM ---------- Previous post was at 10:56 AM ----------
slaphead20 said:
Well spotted jj, I missed that he had used Rom manager
Click to expand...
Click to collapse
But I didnt used Rom manager and have the same problem.
Why it happend overnight?
JJEgan said:
USB Jig will only enable the phone to boot to download mode if the buttons dont work .
As its small cost always worth a try with no warranty phones .
My guess ROM Manager is the problem
CWM
Not compatible with ROM Manager ! Use the CWM Manager provided instead (installed by CF-Root automatically)
jje
Click to expand...
Click to collapse
Ooops. And, if that were the case, what should I do to fix it? (if possible)
Silhaut1 said:
Hi All,
I have the same problem. I am using Omega 27.2 and latest syiah kernel. I tried to dual boot with rom supernexus. Everything was fine when I went to bed. But in the morning I was not able to switch the phone on. I tried new battery, nothing. I tried to charge both batteries, nothing. I tried to press buttons for download mode, nothing. Iam really worried about it now. Please help.
Friend have USB JIG so I will try it tomorrow and let you know. But still if you have anything else, let us know.
Thank y ou
Click to expand...
Click to collapse
Did you have any luck with the USB JIG?
reycat said:
Did you have any luck with the USB JIG?
Click to expand...
Click to collapse
Hi, sorry for delay in response. I didnt have luck with usb jig. Phone is dead. I am sending it to samsung service. Hopefully my warranty will not be broken.
Cross your fingers
Lukas
Silhaut1 said:
Hi, sorry for delay in response. I didnt have luck with usb jig. Phone is dead. I am sending it to samsung service. Hopefully my warranty will not be broken.
Cross your fingers
Lukas
Click to expand...
Click to collapse
Thanks for your answer. I bought an USB JIG online but since it's taking longer than expected to arrive, I couldn't wait any longer and sent the phone to Vodafone's repair service.
Let's hope we both are lucky
have you flashed root before recovery?
reycat said:
Thanks for your answer. I bought an USB JIG online but since it's taking longer than expected to arrive, I couldn't wait any longer and sent the phone to Vodafone's repair service.
Let's hope we both are lucky
Click to expand...
Click to collapse
I was. I've my phone back.
In case someone is interested, the diagnosis was "Faulty electric component" and the fix was replacing this:
GH82-06521A-A/S ASSY-PBA MAIN(COMM)GT_I9300
No clue of what it means, just thought I'd copy it here in case it helps someone
reycat said:
I was. I've my phone back.
In case someone is interested, the diagnosis was "Faulty electric component" and the fix was replacing this:
GH82-06521A-A/S ASSY-PBA MAIN(COMM)GT_I9300
No clue of what it means, just thought I'd copy it here in case it helps someone
Click to expand...
Click to collapse
Iam still waiting for my phone, hopefully it will be back next week.
Finger crossed
reycat said:
I was. I've my phone back.
GH82-06521A-A/S ASSY-PBA MAIN(COMM)GT_I9300
Click to expand...
Click to collapse
Thats the main printed board assembly or, in a more common word, the motherboard.
There's an increasing number of these "random brick" stories, including mine this morning. Here's another thread just like this one: http://forum.xda-developers.com/showthread.php?t=1970422