Related
Hi,
I tried flashing the phone with Clockwork. Part of the way through the flash it started writing in large letters going off the screen (weird text) then screen turned off, and back on to the installation progress, and then it shut off. No response from anything.
I did a battery pull after 10 mins to try to get the phone into recovery, but the phone does not respond to any combination of keys, battery pulls, and connecting the phone to the PC does nothing. The computer does not see the phone, the USB controller in hardware management does not refresh and show anything when connecting while holding both volume keys, and I have tried everything I could google.
There are no lights on the phone when pressing power, or any combination of recovery keys. Screen is permanently off.
Is there a way to force the phone to boot into any mode to get any recovery?
Thanks for the info.
The T-Mobile Vibrant and the Bell Vibrant are not the same and are quite incompatible actually. Did you flash something for the T-Mobile Vibrant instead? That could be your problem. If so, you'll need to be more careful in making sure it works on the "Bell Vibrant" since most of the stuff here is only tested on the US TMO Vibrant. The big letters are pretty common / normal when flashing a ROM kernel, modem, etc. It would help to know what OS version, ROM name / version you were running before and what filesystem (RFS, EXT2, EXT4). You might also mention what you tried flashing and the version of the Clockwork you were using if you can remember.
Even though you say it doesn't respond to charging, does that mean when you plug it into the "Wall Outlet" as well as the "Computer"? They have been known to produce different results. If you can get it to show the Green battery charge screen, there's a good chance you'll be fine.
Have you seen / read this thread before? - http://forum.xda-developers.com/showthread.php?t=848737
Failing that, you might wish to try the USB JIG method to try to see if that will get you into "Download Mode".
I was trying to flash from Stock 2.1 to Axura2259VE. Not sure what File System.
Only tried charging on computer with no response. will try a dedicated usb charger.
I was using the latest version of Clockwork as of today (Updated from app store, Jan 5).
I will put the jig together tonight if possible.
The phone is a GT-I9000M if that helps.
"If your phone screen is always black, that is it does not display the white Galaxy S/Samsung/AT&T logo when you switch it on, then sorry, this jig will not help you."
http://forum.xda-developers.com/showthread.php?t=819551
So, the Jig will not work for my situation. Anything else I can do? The phone was bought on classifieds and only bricked when updating.
Yes, that's the proper model # for the Canadian Vibrant. The US Vibrant is T959. I'm not sure Axura2259VE for T959 is compatible with the Bell Vibrant as the developer (Master) only owns a US model AFAIK. Try the dedicated charger that came with the phone plugged into a wall outlet with no extensions in between. Mind you, I've not troubleshooted a Bell Vibrant before so I don't know how it differs.
The Filesystem is RFS when stock, EXT2 if you applied the OCLF lagfix from RyanZA (not recommended) and EXT4 if you're running VooDoo. By asking about the filesystem, I was just wondering whether you had a lag fix installed / in-use before flashing. Does any of this apply to you?
I have installed lag fix following the tutorial from the app store, but it was for the intent of rooting the phone, which was already rooted. nothing else was run in the application unless it runs the lag fix by default. doubtful. I do not think it was applied.
Phone not under warranty because i bought it from classifieds. Hoping to get it fixed myself so will try to assemble the 301k resistance between pins 4 and 5 and try it tonight.
Any other ideas?
I really don't know what else to suggest to you. However, installation of the lagfix was unnecessary to have obtained root access on the phone. Rooting and Lagfixing are separate processes. If it was both rooted and lag fixed then which app from the Market did you use to apply the lagfix? Did you disable the lagfix before flashing?
RyanZA's OCLF 2.0.
I had it installed, never ran the lag fix, so I do not think this is the case here.
Thanks alot for the replies. I will post results tonight.
eugenek5 said:
I was trying to flash from Stock 2.1 to Axura2259VE. Not sure what File System.
Only tried charging on computer with no response. will try a dedicated usb charger.
I was using the latest version of Clockwork as of today (Updated from app store, Jan 5).
I will put the jig together tonight if possible.
The phone is a GT-I9000M if that helps.
Click to expand...
Click to collapse
The latest Axura flashes the bootloader to your phone. I suspect this is what the problem is and why you are unable to recover from it. I know absolutely nothing about the Bell Vibrant, but flashing a bootloader will affect how you get into recovery/download mode [I THINK]. You could try entering download mode the way U.S. Vibrant owners do, but I'm not sure if it will help. Sorry I don't have any helpful information, just thought I'd note the possible cause for your grief.
Interesting. I hadn't realized that or looked to see if that was the case. That definitely makes sense. Bootloader bricks are the hardest to recover from IMO (if you can at all). At least, in the future the OP should be able to tell if any rom if going to update the bootloader if it contains an "SBL.bin" in the package.
What?!? I'm suprised a ROM was packaged with the bootloader. To me flashing the bootloader is risky business. I'm not sure there's a way a consumer can recover from a failed bootloader
silow said:
What?!? I'm suprised a ROM was packaged with the bootloader. To me flashing the bootloader is risky business. I'm not sure there's a way a consumer can recover from a failed bootloader
Click to expand...
Click to collapse
I haven't flashed the new Axura because of the inclusion of the bootloader [SBL.bin] and truth be told I was shocked when I saw it in there.
So you guys are saying that the Jtag way does not work? I am sitting here trying to connect 2x150K resistors to pin 4-5 and it is not doing anything.
eugenek5 said:
So you guys are saying that the Jtag way does not work? I am sitting here trying to connect 2x150K resistors to pin 4-5 and it is not doing anything.
Click to expand...
Click to collapse
This method is to help you get into download mode if you are "hardware locked". In your case you have the wrong bootloader on your phone. At this point there is not much you can do yourself. The bootloader will need to be reflashed and as far as I know that's only possible with external equipment rigged into your phone.
I think other people were able to recover from the same incident. they just went to a phone technician(i don't know what do call that) and they just flashed a bootloader to your phone and it wil be flashed back to stock.
hey i'm not sure about this because i have only read about it and i really can't remember where because a lot of bricks already happened here.
Sent from my SGH-T959 using XDA App
Hard brick and fix not working
SO...
My vibrant is bricked, and I have my brother's vibrant to reference. (GT-I9000M)
This is a hard brick, with nothing showing up on the screen.
I have ordered the JIG thinking this would solve the boot issue, but with no luck.
I have tried the following:
- Up/Down - USB - Battery - Release keys
- Up/Down/Power - USB - Battery - Release keys
- JIG - Battery
- Battery - JIG
- USB - Up/Power/Menu - Battery
- USB - Down/Power/Menu - Battery
I have confirmed that the second vibrant that is working fine boots from the JIG successfully. I have also confirmed that the battery is working fine and tested on the other phone.
Cause: Battery pull on unsuccessful flash.
Please help! This phone has been bricked for 2 weeks and I want it back to working. I am out of ideas!
I had my phone hard bricked literally 4 days ago. I called T-Mobile and now I'm typing to you from the new phone. Call and see if the phone is still under warranty. If not then you'll have to pay Samsung themselves to fix the issue for you. I don't know what they'll charge, but I'll assume no more than $60 since its a software issue.
Sent from my SGH-T959 using XDA App
OuncE718 said:
I had my phone hard bricked literally 4 days ago. I called T-Mobile and now I'm typing to you from the new phone. Call and see if the phone is still under warranty. If not then you'll have to pay Samsung themselves to fix the issue for you. I don't know what they'll charge, but I'll assume no more than $60 since its a software issue.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Bought from Classifieds so not sure if it is covered. I have contacted repair places around Toronto.
Any advice would be awesome.
Not sure if there are differences for Download mode but the I9000 forum might be better than the US Vibrant forum.
eugenek5 said:
Bought from Classifieds so not sure if it is covered. I have contacted repair places around Toronto.
Any advice would be awesome.
Click to expand...
Click to collapse
I bought mine off craigslist from a private seller. Its worth a try. The most they'll say is no. Just don't say you rooted your phone.
Sent from my SGH-T959 using XDA App
T-Mobile is shipping me a new phone to replace the one I have which has a bad USB.
The question is, what if I can not get the phone back to stock (cause of the bad USB)? I am now running a CM7.1 nightly.
If I do nothing (and keep CM7 on it), will I get backcharged for anything?
I can sometimes get the USB port to work for a short time. I can try to ODIN back to stock, but if I can not get the ODIN to complete, I can also run the risk of bricking my phone. Should I try anyway?
Is there any way to flash back to stock without ODIN?
Thanks
yes, need unrooted stock
Odin back to stock and format your sd card. Basically do a full wipe. This happened to me once and they never found out.
Simply Honey 5.0 w/ 1.2 Bullet kernel. Badass Rom \m/
That would be nightmare for me or anyone in general...have you tried a different USB cord? That worked for me when I thought my USB port was "broken".
duboi97 said:
That would be nightmare for me or anyone in general...have you tried a different USB cord? That worked for me when I thought my USB port was "broken".
Click to expand...
Click to collapse
I fear that it is a nightmare. I have 3 USB cords and can't get a reliable connection with any of them.
Sent from my SGH-T959 using Tapatalk
This happened to me before. If you can still connect even at an angle try to Odin it. If you brick it just say you tried to reformat it and it bricked on you. Yes it's scum bag status doing that but what else can you do when your broke
Sent from my SGH-T959 using XDA App
Logically the idea of a carrier physically checking every warranty exchange is ludicrous, when i sent mine in (7 months ago) i didn't even bother flashing to stock. reason it's ludicrous is because they're just boxes all these bad boys up and sending them back to samsung for a credit.
so about 2 weks ago i did the ota update to android 3.2. ever since then my tab has been acting crazy. it wont recognize charging unless i restart it plugged in. it will say mtp connected plugged in or not to usb. if plugged in the wall i cant turn it off it just boots itself back up. im trying to root but i cant get this thing to do SH*T. ive re installed drivers multiple times and if i go to device manager it wont show tab. any help would be great guys and gals
im running the ota update 3.2 for a few weeks now, no issues really other then a few tweaks I did to make the device fasters, I would suggest doing a factory reset via the settings menu, backup yer data first!! as for the drivers, the fastest way to get them to work is to install kies for galaxy tab, google it...my galaxy tab 10.1 is actually rooted, overclocked, and running a custom kernel...so its pretty fast, but even with all stock I have not had the problems you are talking about.
theandroidnerd said:
im running the ota update 3.2 for a few weeks now, no issues really other then a few tweaks I did to make the device fasters, I would suggest doing a factory reset via the settings menu, backup yer data first!! as for the drivers, the fastest way to get them to work is to install kies for galaxy tab, google it...my galaxy tab 10.1 is actually rooted, overclocked, and running a custom kernel...so its pretty fast, but even with all stock I have not had the problems you are talking about.
Click to expand...
Click to collapse
Well now I'm rooted running ics rom and over clocked, but my tab for whatever reason doesn't recognize being plugged in USB or ac. It did this prior to root but after 3.2 update. Like right now it says 3% battery and I need to plug it up. Problem is that its currently plugged in to AC charger. I can get it to sometimes recognize the plug if I restart it multiple times with plug in. If I power off then plug in it automatically powers up.
I just restarted while plugged in AC and it now says battery at 100% lol this thing is nuts.
Sell it to a developer really cheap, do a warranty exchange, ODIN back to stock and repeat.... I assume drivers on the PC are not the issue.
Yeah the PC drivers are fine. I really don't want to sell it or have to do the warranty exchange. If I send it back I'll have to unroot. Not to mention not having it for a while.
^ then keep pulling your hair out
Honestly, I understand. Also hate when people send devices in for warranty stuff.... but your issue sounds legit. I would be concerned if there was an issue with the charging port long-term.
ok so they said they would fix it but im trying to unroot and i need the stock recovery i downloaded the zip files for dummies and tied to use odin3 to flash the stock recovery that cam in the zip but it keeps failing.
so i just kept restarting into download mode and it finally worked
now that i have it unrooted its on 3.1 i need it on 3.2 before i send it back. i tried to do the update from the tab but it did one update but not for android 3.2.
So Im probably gonna send my tab back tomorrow. Do you guys think they will give me crap because my tabs now on 3.1 when I complained about an issue after update to 3.2?
xanmanz31 said:
So Im probably gonna send my tab back tomorrow. Do you guys think they will give me crap because my tabs now on 3.1 when I complained about an issue after update to 3.2?
Click to expand...
Click to collapse
If the issue is still happening, then no because its a hardware issue. Root or 3.2 didnt break it as the ODIN proved. Silly question, but you did try a different cable? And unless 3.2 changed something, only pershoots kernel allows for actual USB charging, stock TWUX never supported it. Only accepted a 2amp 3.7v on the correct cable (power wires are switched or something).
Sent from my SPH-D700 using XDA App
no i didnt try another cable and for me to run odin i had to restart the tab many times and when its plugged in the wall sometimes it recognizes and sometimes not when i plug in usb it wont mount storage or even to kies like the tab will show connected but the computer wont recognize tried all usb ports. i figured they might ask how i got it to 3.1 after doing the update without rooting i put stock recovery back on also to completely go back stock
xanmanz31 said:
no i didnt try another cable and for me to run odin i had to restart the tab many times and when its plugged in the wall sometimes it recognizes and sometimes not when i plug in usb it wont mount storage or even to kies like the tab will show connected but the computer wont recognize tried all usb ports. i figured they might ask how i got it to 3.1 after doing the update without rooting i put stock recovery back on also to completely go back stock
Click to expand...
Click to collapse
Definately sounds like a cable or 30 pin port issue. I will mention that Samsung has always been cheap with their cables on their phones anyway, but I haven't had an issue with the tabs. Onboard USB ports are the only ones I trust. Too many issues with front panel ports in the past with ODIN. I wouldn't worry about 3.1 vs 3.2 though. Of course you could always put 3.2 back on, I think there is an ODINable 3.2 around somewhere, but its been a while since I looked. Send it back, or try a different cable.
Sent from my SPH-D700 using XDA App
Got the tab back and rooted again with ics rom. Ended up replacing 30 pin port.
Sent from my GT-P7510 ics
-----------------------------------------------------------------------------------------------------------------
So I am on stock but somehow, KIES wont work. It keeps saying connecting, but wont go further than that.
USB debugging is unchecked so I am sure that it not the problem. I heard T-Mobile for ICS upgrade, so I just wanted to be prepared for ICS update for ATT, but idk, why KIES is not working.
Any suggestions?
Bent USB prong in the phone? I've had to adjust mine several times since I got it launch day. Or hardware failure. When my USB was bent it could still charge via a wall charger
Sent from my SGH-I777 using Tapatalk 2
yeah I think it works when i use at a certain angle.
I am trying to go back to the stock rom and hopefully i can return it, but for some reason Odin is not recognizing it. I mean the yellow box of COM:0 does not show up in the "I777UCKH7-CL503881-No-BL.exe"
Do you know the reason for this?
Missing driver.
IIRC I believe you were supposed to install KIES and another Samsung driver...but I remember using my phone on a netbook without it and it worked...
Try installing the USB driver on the official samsung website? I can't post links yet or I would link it...
jjack0310 said:
yeah I think it works when i use at a certain angle.
I am trying to go back to the stock rom and hopefully i can return it, but for some reason Odin is not recognizing it. I mean the yellow box of COM:0 does not show up in the "I777UCKH7-CL503881-No-BL.exe"
Do you know the reason for this?
Click to expand...
Click to collapse
There can be multiple possible reasons. You've eliminated some of them. Could be a failing usb port on the phone, bad cable, etc.
If you can't get usb to work, you can flash back to stock using mobile odin. I assume you are rooted. Just download the one-click downloader to your phone over wifi, or use dropbox or something to get it onto your phone. Mobile odin will recognize and flash from the one-click downloader. There is even a guide in the general section on how to do this.
creepyncrawly said:
There can be multiple possible reasons. You've eliminated some of them. Could be a failing usb port on the phone, bad cable, etc.
If you can't get usb to work, you can flash back to stock using mobile odin. I assume you are rooted. Just download the one-click downloader to your phone over wifi, or use dropbox or something to get it onto your phone. Mobile odin will recognize and flash from the one-click downloader. There is even a guide in the general section on how to do this.
Click to expand...
Click to collapse
Creepy just posted this while I was getting you the link for the guide to return to stock with no PC: http://forum.xda-developers.com/showthread.php?t=1691659.
I returned to stock, and I think I figured out the problem as well.
The problem I am quite sure is the USB port on the phone. Like I said, when I keep the USB cable connected at a certain angle, it works just fine.
I will just have to live with it now I think because ODIN displays custom binary installed and the count is 2, so I dont think ATT will let me exchange the phone for a new one.
jjack0310 said:
I returned to stock, and I think I figured out the problem as well.
The problem I am quite sure is the USB port on the phone. Like I said, when I keep the USB cable connected at a certain angle, it works just fine.
I will just have to live with it now I think because ODIN displays custom binary installed and the count is 2, so I dont think ATT will let me exchange the phone for a new one.
Click to expand...
Click to collapse
ehhh, its worth a try. Thats a hardware failure, the one that samsung is known for. Mine is starting to go out too.
I've returned 1 rooted phone with this issue, and warranty'd 1 rooted one that had a broken LCd.
These were Infuse's but same damn samsung problem.
MotoMudder77 said:
ehhh, its worth a try. Thats a hardware failure, the one that samsung is known for. Mine is starting to go out too.
I've returned 1 rooted phone with this issue, and warranty'd 1 rooted one that had a broken LCd.
These were Infuse's but same damn samsung problem.
Click to expand...
Click to collapse
Yeah I am surprised these hardware problem are so common.
No wonder most people are crazy about Apple sells so many iPhones
I had the very same issue as you are describing.
All you need to do is tweak the USB port a little. Did mine about 3 or 4 months ago and have not had to touch it since.
Use a small precision screw driver, fold a couple layers of Kleenex over the tip and gently bend it towards the screen side of the phone.
It WILL work perfect after that.
Sent from my SGH-I777 using xda premium
dschreiber69 said:
I had the very same issue as you are describing.
All you need to do is tweak the USB port a little. Did mine about 3 or 4 months ago and have not had to touch it since.
Use a small precision screw driver, fold a couple layers of Kleenex over the tip and gently bend it towards the screen side of the phone.
It WILL work perfect after that.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Will try it for sure. Thank you for mentioning which way to bend the port towards. lol
So I am on stock but somehow, KIES wont work. It keeps saying connecting, but wont go further than that.
USB debugging is unchecked so I am sure that it not the problem. I heard T-Mobile for ICS upgrade, so I just wanted to be prepared for ICS update for ATT, but idk, why KIES is not working.
Any suggestions?
jjack0310 said:
So I am on stock but somehow, KIES wont work. It keeps saying connecting, but wont go further than that.
USB debugging is unchecked so I am sure that it not the problem. I heard T-Mobile for ICS upgrade, so I just wanted to be prepared for ICS update for ATT, but idk, why KIES is not working.
Any suggestions?
Click to expand...
Click to collapse
Try uninstalling/reinstalling. That would be my first step.
Sent from my SGH-I777 using xda premium
dschreiber69 said:
Try uninstalling/reinstalling. That would be my first step.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I did that like two times already.
I even flashed a different stock Rom. I mean I started with The kernel + rooted UCKH7
but then since it didnt work, I tried Kernel + cache + rooted UCKK6 package from:
forum.xda-developers.com/showthread.php?t=1286432
I'm not an expert at ROM's and all that. But my wife's Ebay International 9205 kept having out of memory errors even after cleaning, cleaning cache and apps and I finally bricked it. Or at least to me it's a brick. I can't get it to recognize Samdung USB drivers on a PC anymore for Kies. I think PDAnet drivers work for Odin.. It lets me try and Odin flash it, but always fails. I gave up and bought her a new http://www.geekbuying.com/item/Tron...00P-2GB-16GB-5MP-13MP-Dual-Camera-324755.html instead. She's only 4'10" and I think she compensates for her size with big phones
So what do I do with the old Mega? It's supposedly under warranty from Samsung England but they don't answer my emails. It shows good ROM/Blah whatever like they will still fix it. I have dreams of fixing it but at the moment I'm ready to just dumpster it. Wife wants to send it to her family in Philippines. They have real cell phone shops there unlike USA where I'm at. So should I sell it? Pay to fix it? It's nice, but a paperweight to me as it is. It's a waste of my time. I got enough hours into it now.
- Joe
How did you manage to get it bricked?Have you tried flashing your original firmware thru Odin?Maybe problems with USB drivers.Try re-installing Samsung Mobile usb drivers and un-install Kies 3 if its in your PC.I have a Mega 6.3,almost every custom rom cooked here I have flashed with success.And even stock firmwares in sammobile.com.Yes,I am from the Philippines,sure they will fix it there.
P.s.Have you ran Odin as administrator?
Sent from my SM-N7505 using XDA Free mobile app