[Q] Utterly dead Vibrant - Vibrant Q&A, Help & Troubleshooting

Hey there.
First post. I used Odin 3.1 to flash Froyo 2.2 on my Vibrant that was running Eclair 2.1, and Odin showed a successful completion. The phone then turned off and instead of re-booting, has become totally, utterly unresponsive.
I have tried a number of ways to get it to work, or at least get in to Download or Recovery mode, including the "remove everything, then re-insert battery while holding down volume up/down keys" and any number of key combinations. I've trowled the forum and haven't found a single solution for a completely unresponsive Vibrant. even the USB jig seems to be for those phones that at least show the Vibrant Logo or the "S" at start-up, while mine doesn't do anything.
The only encouraging thing has been posts by people who claim to have lefft their unresponsive Vibrants plugged in for several hours only to have them miraculously revive, but that seems like a long shot to me.
Have I managed to do the impossible and brick an unbrickable phone? I'd really appreciate help as I just got the phone last week and don't want to declare it a dead loss so soon.
Cheers!

Utterly, haha
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thinking.. above was a joke...
What ODIN files did you flash? Link to them?
What version of ODIN, the latest?
When you say nothing... you mean you can't see anything on the phone, regardless of the action?

rofl OMG is that chick half naked hahaha seriously is she in her undies milking a cow WTF! LMFAO!
- so the phone won't turn on huh?...... no power at all?....... how about plug in the cord, do you see the batt charge?

haha utterly.. when you say put in the battery while holding the volume keys, did you put in the battery or plug in the USB??

I had to replace mine. Been good ever since.
Sent from my GT-I9000 using XDA Premium App

Here's the long story. My phone was getting the 'device unrecognized' error in Kies and Kies Mini, so I used Odin 3.0 to flash it, using the "T959UVKA6_REV05_home_low_CL860813.tar.md5" file.
After flashing, my phone wouldgo into recovery mode and the following error.
"E:Cant mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:cant mount DBDATA:
copy default media content failed."
Next I followed the steps detailed in this post . When I flashed my phone according to the 'Gauranteed Solution', my phone turned off at the end of the flash and has stayed off ever since.
And when I say nothing, I mean nothing. No battery symbol, no sound, no Samsung Vibrant logo, nothing. Just a blank screen.
I tried plugging in the phone and then putting in the battery with the volume keys pressed and I also tried it without plugging in the USB. Either way, nothing happens.
As you can probably guess, I'm a n00b of the first order and I fear I might have killed my phone.

If you do manage to revive your phone back.. You better flash roms via cmw. Not that odin isn't great but cmw never caused any problems(to me).

Make a jig to force download mode then reflash stock os and install rom manager to flash roms. P.m for more Info.
Sent from my SGH-T959 using XDA Premium App

Thats funny, the last post in the link you referenced is someone having the same problem as you........ why would you try to do that? and the .tar is some I9000 file being that the (fix) was in the I9000 forum. Neither of these probably have anything to do with your problem now i just thought it was funny. I mean why wouldn't you just use the T959UVJFD.tar in ODIN?
It seems that the "E:cant mount" error is a fairly common issue and from what i am seeing alot of the people having this issue after using samsung kies are getting replacements fairly easily although it is a last resort for many. I would not think its an issue with your drivers or anything like that, probably just ODIN being weird. Don't give up on ODIN i would assume that it will recognize the phone eventually as most "DEAD" vibrants do after time. I'll keep looking into it for you. Hope you find a fix soon. Good luck!

You can also restart the computer and f8 and turn off driver signing and see if that helps. Once again I don't mind helping on a more personal basis. P.m me.
Sent from my SGH-T959 using XDA Premium App

have you ever actually tried a usb jig ?
http://cgi.ebay.com/ws/eBayISAPI.dl...83134&ssPageName=STRK:MESELX:IT#ht_723wt_1139

Related

[Q] Removie yellow tringle

Salam,,,,
i just bought my galaxy s ii yesterday with stock 2.3.4
i think that i followed all steps for "rooting thing"
after load "CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4" in Odi3 v1.85
when i clicked start it says pass, but the last message in the box it says: Removed!!
then i got the yellow triangle, i tried to do the same step again and again, and sometimes load "KERNEL_I9100XXKG2_CL375027_REV02_user_low_ship.tar.md5"
i cant start my phone!!
help please
my apologies
now i got this problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Simple to remove yellow triangle: USB Jig
Second problem, try holding down Power + Vol Down + Home buttons together when the phone is off, until you see a verification popup saying if you want to continue to flashing a custom ROM. Then try reflashing your ROM or kernel.
well, in my country there is no USB jig unfortunately
second i got this problem in my second replay (look image)
there is no use when holding power+home+volume down or up
the same problem appear to me
thanks for your help
I doesn't matter if it's not in your country. Order one here:
http://usbjig.com/
Did you enable any of the checkboxes that were disabled when you started Odin?
Like "Repartition" or "Flash Bootloader" or any of those?
yes, all three was checked when i used PIT, PDA, PHONE, and CSC
There we are. The Galaxy S 2 does not need a pit file, you probably got a pit file for a Samsung Galaxy S.
<Warning information heard from other users>
In another big Android board is a discussion going on that flashing a pit file can fry the mainboard + battery as it will use wrong settings (the settings for the Galaxy S) and apply a too high voltage.
</Warning information heard from other users>
From my experience in that case even the jig does not work anymore (you could try it anyways) so you might either need to send it to Samsung or find somebody with a JTAG (won't help if the mainboard gets damaged).
@prodygee
i hope it doesnt take long time in delivery
ohh, dont tell me that the board is damaged
i didnt spent 24h yet!!!!
DBGT_87 said:
ohh, dont tell me that the board is damaged
i didnt spent 24h yet!!!!
Click to expand...
Click to collapse
Nah, as I said, those are just reports from other users I couldn't verify (I'm not gonna flash a pit file just for the sake of testing!) so you should try the jig anyways, because it's not expensive and does the trick in many cases.
However if those user claims are correct not even a JTAG could help but let's just hope the best for the moment, there's no point in being scared beforehand.
I wish you luck and please tell us if the jig worked!
If you want to remove the yellow triangle and you don't have a jig it will be simple..
Flash Cf-Root
Flash stock kernel (cwm for cf root will remain)
Unzip the Cf root you falshed earlier until you get zImage and don't rename it
Open cwm
Choose flash kernel
Select the zImage you extracted and flash
After that there will be no yellow triangle after boot
Sent from my GT-I9100 using xda premium
@ephraim033
my friend i cant go to download mode anymore
how much do you think it cost when the board is damage more than $200?
i will try warrant company, then try jig
I see.. Why don't you take it to damsung service center and make a story that you updated through kies then kies broke your device.. Atleast try the service center because it's free, but if all else fails you can try jtag
Sent from my GT-I9100 using xda premium
oh man, i just take it to warranty company, they told that they will try to update the software (i think it wont work) otherwise they will give a new one!!
Why are you flashing anything without not knowing what your doing?!
Sent from my GT-I9100 using Tapatalk
they gave me a new, told me that your problem cannot be fixed
they will send the phone to Samsung!!

[Q] Help PLZ! :(

First off, I would like to say sorry if this is the wrong section to post this. I'm a total noob
Secondly, I don't have a Vibrant, I have a Samsung Galaxy S 4g. I couldn't find a specific thread for my phone but I was guessing I should post it here because I thought that they were pretty close? The Vibrant being sgh-T959 and S4g is sgh-T959V, so I'm hoping I can get some help here.
I've literally spent about 16 hours or more trying to fix my phone (2 days).
Here's what happened:
I flashed my phone with Heimdall following instructions here at this forum: http://forum.xda-developers.com/showthread.php?t=1358498. At the very bottom of the first post is the download section and I downloaded the 2nd choice which I believe is "Download KJ1 Kernel Stock Rom with Bootloaders". I only flashed my phone because it was having problems.
I went and flashed my phone and it worked! It was working fine until I went to RootExplorer changing permissions on a txt file and my phone froze (I don't think changing permissions on the txt file was the problem). So I reseted my phone by holding the power button down until it boots up and then I got stuck in some kind of boot loop (where the phone keeps rebooting after samsung galaxy logo). So I thought the only way to get passed this is to reflash the phone with the same procedure I did earlier.
I put the phone in download mode and went on with the flashing. For some reason it got stuck and it wouldn't finish. On the Command Prompt, it got stuck at this:
[C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\heimdall-win32\heimda
ll.exe, flash, --pit, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\
Sgs4g.pit, --6, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\zImage
, --7, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\zImage-1, --22,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\factoryfs.rfs, --23,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\data.rfs, --24, C:\DOC
UME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\cache.rfs, --11, C:\DOCUME~1
\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\modem.bin]
And on the other window (Heimdall's window) it got stuck and shows this:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
So what I did was close both windows and tried again. This time my computer couldn't recognize my computer. Then I turned my phone off and tried to go back to "Download Mode" but instead, it showed a "Phone with dotted lines through this yellow triangle and into a computer". So I turned the phone off again and tried and tried and kept trying to put it into download mode but couldn't get it to work. It kept showing the phone, triangle, and computer. Although I did realize that my computer can still recognize my phone at this state.
I tried using ODIN but odin couldn't recognize my phone. Went back on Heimdall and that still recognizes my phone! I was feeling hopeful but whenever I kept trying to reflash my phone, it keeps getting stuck at the same spots that I mentioned above.
Can someone, anyone, please help me with my situation? I'm way to broke to buy a new android. This phone is incredible and I really would want to get it up and running again. Is there a way I can get passed this?
I know this is a lot of time reading this but I would highly appreciate anyone that can help! Please and Thanks you!
Here is the Galaxy 4g threads
http://forum.xda-developers.com/forumdisplay.php?f=1065
Also, (Odin speaking), does this look familiar?
This is for our version of the Vibrant, but you get the idea. You'll need to get the Pit/Tar files from your forum.
http://forum.xda-developers.com/showthread.php?t=1307637
"SOFT" BRICKED WHILE USING ODIN?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are getting a "Phone.. ! ..Computer" image (seen above) when booting phone, yes, you are bricked but it is reversible! Just follow these steps...
Make sure you have ODIN OPEN with admin privileges!
1.) Take off your back cover, remove your sim & mirco sd card.
2.) Remove your battery.
Make sure you have the USB plugged into your PC but NOT your phone!
3.) Hold the volume buttons.
4.) Put the battery in.
5.) Put the USB in.
You don't necessarily need the download mode image to be present. As long as you are getting the COM ID to light up yellow in ODIN, just flash back to stock like normal.
Click to expand...
Click to collapse
Woodrube said:
Here is the Galaxy 4g threads
http://forum.xda-developers.com/forumdisplay.php?f=1065
Also, (Odin speaking), does this look familiar?
This is for our version of the Vibrant, but you get the idea. You'll need to get the Pit/Tar files from your forum.
http://forum.xda-developers.com/showthread.php?t=1307637
Click to expand...
Click to collapse
Thanks for the Galaxy 4g threads! and yeah that does look very familiar its just that I did everything I can to get into download mode but I can't get it to work. Thanks again for the threads!
I remember when I was a noob(no pun) the same thing happened and couldn't get it to do anything for like 4 hours. I think I opened odin took battery out, installed usb to computer, hooked usb to phone, pressed volume up and down simultaneously and installed battery without letting go of the volume buttons (I'm not sure if youll see dl mode on phone),pick your .pit/.tar files and flash away even without the COM showing
On the post above mine I think step 4 and 5 should be reversed

Encryption Unsuccessful? Please Help

So i was using my vibrant running DocMasters ics v5 when suddenly my phone rebooted only to be greeted with this "Encryption Unsuccessful" screen that i've never before seen in my life. Not knowing what to do i clicked on "Reset phone". 1 minute later this "Encryption Unsuccessful" screen appeared again so i went into CWM...factory reset..clear cache...and flashed DocMasters ics v5...again the screen appeared. Finally I decided to start from scratch and entered "Download Mode" and flashed back to stock 2.1...Now my phone goes into a bootloop...and i am unable to enter CWM...dont have access to my internal memory/nor sd card. I've tried everthing I think...but know luck at all. So my point is guys. I officially have the first Soft Bricked Vibrant. Those who said this phone was unbrickable...well i managed to do it...of course unintentionally.
RIP Vibrant: 11/20/2010 to 3/25/2012
Oh here is a screen shot i found of the "Encryption Unsuccessful" screen. I can still enter Download Mode so i guess there maybe hope after all. But i dont know where to start. Any help or advice would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is EXACTLY what happened to my phone too! I made a thread about it... no one was able to find a solution... .
I'm pretty sure its completely bricked, I've tried EVERYTHING. Luckily, I can upgrade in about a week...
Try flashing Eugene's froyo that does not brick.
@lolrus101...Yeah i have tried everthing from flashing back to stock 2.1 to executing adb commands to try and unbrick this phone. I think at this point it is impossible to fix unless Samsung gets a hold of it...wich is not an option since it is out of warranty. Anyways there no need to worry anymore since i just bought a Galaxy Nexus (GSM).
@djquick...Is Eugenes Froyo flashable through odin or heimdall? I cant access CWM only download mode. If not well i give up. I'll just wait till my GNEX arrives.
Thanks for replying guys.
Eugenes that does not brick is odin flashable, just search it.
Cool it is odin flashable. I guess i'll give it one more try. Lets see if this thing really is unbrickable.
I just flashed Euguene's Froyo rom and there are some good signs and bad ones. Well the good news is there is no more boot loop at the first boot screen (Vibrant Samsung logo)...The bad news is there is what appears to be another boot loop at a different boot screen (Galaxy S Animation). After the animation the screen turns completely off and the led buttons stay lit. I let it sit for about 10 mins and nothing happened. I followed every step in Eugene's guide inlcuding the adb command "adb reboot".
I'll reflash it and wait a little longer lets see if it works.
If you got past that stupid message, just reflash to a regular stock rom 2.1.
Here's a link to help: http://forum.xda-developers.com/showthread.php?t=848737
Follow the directions to a T. Usually works like a charm everytime
I give up
After flashing Euguene's rom nothing happened. Then I flashed T959UVJFD.tar
stock 2.1 and i get the same results. Well i guess this is it then. This phone is officially "soft-bricked". I think i've tried almost everything now. I can wait till my new Galaxy Nexus arrives. This phone i will not root i don't want to brick it like my vibrant.
Even though i wasn't able to fix my phone i truly appreciate the help guys.
Thank you.
I actually just picked up a T-Mobile Nexus S GT-I9020T also and I rooted it as soon as I took it out of the box
Ha that's one thing i probably won't do this time. The only reason i decided to root my phone in the first place was to get an AOSP android build and to get rid of all that Samsung and Tmobile bloatware. Of course rooting my phone won't be necessary this time since my new Galaxy Nexus GT-i9250 will come preinstalled with the latest google build in ICS. Along with that it will not have any bloatware from any carriers since it is unlocked
OP, I kow you already got your GNex but when you got this error, OP, what ROM were you running? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
See here for possible work-around

[Q] I beseech thee, help me diagnose my YP-G70!

I've been searching XDA and Google for months now and I haven't found anyone else with this precise issue. I'm very tech savvy, but this is just beyond me! What say you? Will you help me in my quest to diagnose my device and possibly find a cure?
Listed below is what occurs when the USB Cable is connected, either via PC or the Wall.
While USB Cable is disconnected:
Pressing or holding any of the buttons, together or individually, does absolutely nothing. (But the battery can't be dead. I've had the thing on charge all night!)
When USB Cable is connected:
http://youtu.be/J8FJSo_S7cQ
Without pressing anything, the device powers on into download mode and continues to reboot itself every few minutes.
Holding the power button (or all buttons together) reboots it back into download mode to repeat what I just described above.
Pressing any/all buttons at this point does nothing.
When I disconnect the USB Cable from the device while in Download Mode, the device shuts off after about 20 seconds.
I have seen this on occasion, but nothing different happens:
(I'm aware this means forced download mode.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm able to use Odin completely normally and flash anything successfully as well. Yet it just reboots back into download mode. And if I leave it alone while connected to my PC with Odin up, this is what it looks like:
I've "successfully" installed Stock ROM, Kernel and PIT files. Nothing changes! I've also tried one-click unsoftbricker, heimdal, calling it names, begging it to work. Am I crazy or...is this thing done for?
Have you tried repartitioning it?
By clicking that check box in Odin? Yes.
Ah, you must've hardbricked your Galaxy.
http://forum.xda-developers.com/showthread.php?t=1496360 < See if anything in that topic helps you.
You need to flash a ROM that has boot loaders in it...
When you use the unbrickable resurector, it flashes a boot loader that always boots to download mode. From download mode, you can flash a FULL rom, that will replace the boot loader. Then it will boot normally.
TheKryptonite said:
Ah, you must've hardbricked your Galaxy.
http://forum.xda-developers.com/showthread.php?t=1496360 < See if anything in that topic helps you.
Click to expand...
Click to collapse
Thanks, I've been suspecting hard brick. I've seen that thread before, it could really use some reorganizing. I can barely follow it.
Meticulus said:
You need to flash a ROM that has boot loaders in it...
Click to expand...
Click to collapse
That would make sense but which ROMs would those be?
This is a Russian ROM but it should have boot loaders.
http://www.4shared.com/zip/vxHoJ8E0/G70JKKE3_STOK_222RU_.html
Let me know how it goes...
Downloading now. I'll have to try it tomorrow on spare time. Really hoping this works. Thanks for giving me some hope, I really thought this thing was done for!
It's not hard bricked... that ROM will restore it. But after you flash that rom , you'll need to flash a different Rom for your region...
Meticulus said:
It's not hard bricked... that ROM will restore it. But after you flash that rom , you'll need to flash a different Rom for your region...
Click to expand...
Click to collapse
I never even heard of a "Full" ROM before. The problem I was having was apparently my bootloader - or lack-there-of.
You saved my Galaxy Player's life! Thank you very much!
I'm happy to say that this case is closed!
I am going to favorite this thread. You never know when you'll need some good info like this.
Ironically, my GP just managed to softbrick -_- I may be f'd.
Edit: Thankfully, I managed to fix it. Whew!

HELP ! Dead S4 after ODIN

I was runing 4.2 with MKD build number, tried to update via ODIN to 4.3.3 with his flash image
http://forum.xda-developers.com/showthread.php?p=47011336
Odin gets me this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, i got this message on my phone screen
"firmware upgrade encountered error
please select recovery mode in kies and try again"
I cant get into Download or Recovery mod... or power on the phone!
When i conect it to my pc it reads it like "QHUSB DLOAD"
I instaled the QHUSB DLOAD drivers and the pc recognize it like Qualcom HS-USB QDLoader 9008(COM5)
Odin reads it also (COM5) but i cant reflash it because i cant get into Download mode
H E L P !
ANYONE ? Cmon please.... any ides, tips help ?
AnajaDroid said:
ANYONE ? Cmon please.... any ides, tips help ?
Click to expand...
Click to collapse
If you can't boot it into recovery, it's pretty much bricked. Look around for people offering to JTAG it to recover.
Before I consider helping you, why on earth would you attempt flashing this? Why not instead flash a 4.3 rom? I have to know you were intentionally trying to lock your bootloader before I try to help....it just feels so wrong giving instructions for locking a bootloader
---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------
k1mu said:
If you can't boot it into recovery, it's pretty much bricked. Look around for people offering to JTAG it to recover.
Click to expand...
Click to collapse
I bet it would still get into download mode since aboot wasnt flashed, well I guess it depends on whether or not the phone even attempts to boot or not though. I've gotten my S4 out of qhusb by keep the charger plugged in and constantly removing and inserting the battery.
Surge1223 said:
I bet it would still get into download mode since aboot wasnt flashed, well I guess it depends on whether or not the phone even attempts to boot or not though. I've gotten my S4 out of qhusb by keep the charger plugged in and constantly removing and inserting the battery.
Click to expand...
Click to collapse
Very likely. It's pretty hard to brick this phone into a state where it can't be recovered.
However, I've seen people do amazing things like flashing GS3 ROMs and wondering why they didn't work. Or less crazy, flashing AT&T ROMs on a VZ phone. People that stupid are why Verizon is so anal about locking down their phones.
I was just trying to update it to 4.3 since OTA didnt work I taught this was stock odin flashable image...
AnajaDroid said:
I was just trying to update it to 4.3 since OTA didnt work I taught this was stock odin flashable image...
Click to expand...
Click to collapse
Stock mean locked boot loader!!
What USB cable did you use and what port on the computer? While it's a bit of a stupid question I had a problem like that when doing an ODIN restore and tried all kinds of fixes including a totally different computer and it turns out the USB cable I was using was crap even though it'd transfer files over fine, ODIN didn't like it.
If you can't get it out of QHUSB DLOAD with button pressing, you can try this tool http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable.
LemonSlice said:
What USB cable did you use and what port on the computer? While it's a bit of a stupid question I had a problem like that when doing an ODIN restore and tried all kinds of fixes including a totally different computer and it turns out the USB cable I was using was crap even though it'd transfer files over fine, ODIN didn't like it.
If you can't get it out of QHUSB DLOAD with button pressing, you can try this tool http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable.
Click to expand...
Click to collapse
It was COM3 port, and it was OEM samsung usb cable...
I Tried everything i can but there is no way to get into download/recovery mod...
I had a similar problem the other day, don't worry. Depending on whatever build you were on before you bricked it, download that baseband and odin it on there. It did wonders for me and should work for you.
Solved... The device was hardbricked.... JTAG did the trick, cost me about 35$

Categories

Resources