Related
Hey folks. I'm hoping to get through this in one piece, with one walkthrough.
I recently messed up in flashing a Rom to my Captivate. It cleared the phone of firmware and left me with the AT&T splash screen.
I bought a jig, and am now at the "Downloading..." screen and am trying to take this slowly to ensure a properly functioning phone (I've been without for two weeks now).
I've read through the sticky post [link]http://forum.xda-developers.com/showthread.php?t=884364[/link] and have most of the downloads. The Odin link is dead, and I don't have the proper version (I used a version I later found out was bad).
What I'm hoping for is to get someone to show me where the proper version of Odin is, and maybe give me a quick guide to doing this for a Rogers Galaxy S Captivate.
I hope I'm not coming off as lazy, but I tried this solo, and it went awry. Thanks for any help in advance.
This is the link for Odin. http://forum.xda-developers.com/showthread.php?t=731989
You want to Open Odin, then use the jig to put the phone in download mode, connect usb to your computer and wait until odin recognizes your phone. Click Start and sit back and wait. You should then be able to put whatever rom you want on the sd card and flash
Okay. I got the proper download, and used Odin. It reported success.
I haven't unplugged the phone from the computer yet, but it's also not showing as a drive on my computer. I'm at the stage where I'm supposed to root the phone after using Odin and before flashing.
Should I unplug the phone, or is that going to send me back to square one?
JavaMac said:
Okay. I got the proper download, and used Odin. It reported success.
I haven't unplugged the phone from the computer yet, but it's also not showing as a drive on my computer. I'm at the stage where I'm supposed to root the phone after using Odin and before flashing.
Should I unplug the phone, or is that going to send me back to square one?
Click to expand...
Click to collapse
If you used that Odin 1 click you will have the AT&T version, it will work but you will have the AT&T boot up screen. After it is finished your phone should reboot by itself. If it didn't try pulling the battery and then turn it back on.
Driver Installation Issue at Fault?
Okay, so I'm starting to wonder what's going on with the communication between my phone and my computer. I have the drivers, but when I try to install them (64 bit, for a dual-core, right?), it claims to fail.
I think maybe that this is the reason I can't get the computer to recognize the drive. Also, when plugged in last time, it said it failed to install drivers again. Even when the phone was operational, I had issues with that.
So . . . I'm wondering if maybe I solve that and the issue becomes seamless. Any thoughts on this would be appreciated, as it seems I'm stuck until I get the phone to register. Even Odin won't see it now, although I've already passed that step. F-Bomb.
Did you get the drivers right from samsung web site if not thats why they wont install i had same thing when i got my cappy.
I got drivers from.samsung.com installed em worked perfect sence. i kept the download saved had to install em a few times over the last 9 or so months. Only because of all the dam software hardware i run. Good luck
Sent from my GT-I9000 using XDA App
Just because it's a dual core processor in the computer doesn't mean you have a 64 bit OS.
You might want to know what version of windows you have...just a thought.
Okay . . . I can't seem to resolve this driver problem, nor can I move forward in the previous issue of getting my phone back to a functional state.
I can't imagine what I'm doing wrong that everyone else managed to avoid. Could I maybe request some one-on-one time with an experienced Rogers user? Just to recall the exact steps they took in order to successfully UNSCREW their phone.
Again, I appreciate all the help. Every post is making progress. I'm just frustrated at my ineptness with solid state installations.
I'm still not able to install the drivers or get my computer to register the phone as a drive. I did a bit more reading, but I've found nothing but different driver links. Has anyone else had this installation failure?
I have had driver problems before...try plugging up phone; on computer control panel, device managment , go to were it has device (just click then till se something about samsung) then uninstall drivers, next unplug phone, reinstall drivers that are on design gears (developer) thread for odin one click, next plug up phone sbf it will say new hardware and install drivers then see if that works... Ps if need to just pm me and I will get back to you to try and help
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
A side note: I just tried it from my computer and the link if good and they work
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Try it again, however this time plug your USB cable into the USB port in the back of the computer.
Drivers were installed properly with Toolbox. Thanks for the help
Hey there, i am feeling somewhat overwhelmed with all of the advice going on out there and need someone who can give me the answer to my specific problem hardware wise without breaking a sweat...
I flashed a froyo 2.2 rom onto my phone a while ago, recently all of my apps stopped working, and i could no longer install any apps.
Couple days ago i tried openning gmail and the screen went black and gave me the bzzzzzz...............................bzzz...bzzz...
vibrating error that you usually get when an app crashes.
Now the phone continues doing that even when booted up and stuff
It starts right after the S screen and repeats until the battery is removed.
My phone can't get into download or reset mode using the 3 button method so i bought a jig off of ebay, works like a charm.
however NOW, i cannot get the computer to see the phone; both when it is on and attached and in download mode and attached. Odin can't see it, neither can Kies.
If i can get either to see it, i can look up the flashing process to make sure everything is right.... but as of yet nothing i am doing is making a difference.
Thanks for any help
Ok, I'd focus on odin so disable Kies (in task manager processes - all the kies processes).
Then I would 1) reinstall the drivers (standalone ones) 2) Have a few versions of odin to try (like 1.3, 1.7 and ez odin) 3) Clean your usb port on the phone (and computer maybe too - whats the harm?).
Usually if you are sure the drivers are Ok then you should be able to odin working with a nice clean port. They are more sensitive to dirt/moisture or whatever than they should be.
Try that and let us know...
BTW Some people think that the order is important but I've never noticed that. I always have odin open and then connect it but cant hurt to try the other way around too.
Hey thanks alot,
I am at work right now but i am optimistic about trying that out lol.
Just so i know for when the time comes and if Odin works, what files do i need to flash it? .pit, .tar and anything else specific for Bell Canada?
I only ask because you are with Bell so it is probably a very simple answer for you. Otherwise I am sure i can find it elsewhere.
Thanks,
I'll keep you updated
Josh
Download the complete jl2 rom from link I posted yesterday (search my posts) with repartition ticked, then flash the kc1 rom from stock rom link on xda or at samfirmware.com and flash without repartition if you want the latest. You could just try the kc1 step but I you need to repartition.
Sent from my GT-I9000M using XDA Premium App
Hey man,
my phone has never been sent in for repairs or replaced...
I was reading one of your other posts and you advised another member to send it in and maybe they will replace/update hardware?
I have still had my phone for less than a year so sending it in will be no problem at all...
Should i flash to the latest myself or return to stock and send it in?
I really appreciate your help.
Thanks
Well he knows his is broken as he can see that his internal memory reads 0 (which means its cooked - ask me how I know...) and he was trying to fix it in a round about way. Or there was the guy who flashed a captivate rom - that was just a big no-no.
You might just have a corrupt partition or some other corruption in the file system. I seem to get that all the time and its a pain but very fixable .
Alright, sooo
-uninstall Kies
-install drivers only
-try to connect to Odin
-If succesful flash with Odin
-dance with joy
Got it, I will update you later when i get home.
Thanks
installed drivers on my work computer (32 bit windows xp) and nothing... I've tried phone off, phone on, phone in d/l mode... It doesn't pick up anything...
I can try it on my Windows 7 comp at home and see if that works but i'm wondering what the worst case scenario is just bringing into Bell and having them fix it... Am i looking at charges, warranty voiding, etc.. etc... to have it fixed or could i BS my way out of it?
Fuuuuuuuuuuuuuuuuuu
pretty sure i flashed the wrong firmware on my phone, when it boots up it says GT-I9000 not GT-I9000M.
It worked fine for like 6 months so i never questioned it... damn damn damn
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
I9000 firmware is completely compatible. The text you see is from the kernel which are always for i9000 unless you have one of the three bell firmwares. So that's not the issue.
Sent from my GT-I9000M using XDA Premium App
RogueCow27 said:
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
Click to expand...
Click to collapse
I would keep trying. I have gotten warranty before and I was in the same predicament as you almost except I knew that the internal memory was dead. But that was also around the time when most of the I9000M models were dying. They might be checking more now.
If you get odin to flash a stock rom then you can go for it but by then you should be able to fix it.
Sent from my GT-I9000M using XDA Premium App
Alright i will keep trying.
As far as the firmware goes, my gf and i both have the same phone, but she kept heres official and i put custom roms on mine (just the 2.2 because it wasn't available)
We are both on bell canada so i asked her to boot up her phone and the beginning message on hers says GT-I9000M so it freaked me out lol
I will try on my home computer,
keep your fingers crossed for me
Alright, so Odin can now see my phone (it was the damn cord, my Win 7 comp couldnt see it but my xp work laptop can)
Which firmware would you recomend flashing? Stock gingerbread or a slight variation?
I am at work right now so i can wait a bit for a good response. It'd really help me out if you could provide links and tips to the best firmware out right now (i have no problem flashing a custom ROM if it is good).
Thanks alot,
Josh
Succesfully Flashes Gingerbread 2.3.4
Thanks for all your help!!!
how did you manage to see it in odin?
i have te same problem with restarting just after first screen (after flashing to gingerbread) but i cant see it in odin so i cant flash it again?
when i connect it when turned off, a small icon appears with usb connected sound but its still not visible.
Is it maybe my win7?
help, anyone please
Did you start in Download mod? Did you kill the Kies processes in you Win7 task manager ?
If yes, sometimes Windows takes time to install the drivers (be sure ton be connected to the internet), you should also close and relaunch Odin.
i launched download mode with sdk, and now i cant start it.
i went to another pc with xp. it installs drivers but odin cant recognize it.
Well i did it on my work XP computer becuase WIN 7 wasn't recognizing it. But it turns out the whole time the cable i was using would connect to charge, but not act as a pc connection.
I have done the unfortunate thing and bricked my phone, now I did see a post in here on this subject but I am not able to open this program/app on either Ubuntu or Windows 7 PC's.
Now my questions...
Is this the only way to unbrick my phone?
Using Linux or Windows, which one works better?
I am using the Rogers one i896, the screen just stays at i896. I will explain what I was trying to do, I had installed Clockworkmod on my rooted phone on the intentions to install another ROM on my phone. I boycotted this idea as I saw another way that had me download the zip, enable debugging, turnoff and place into recovery mode...that is where I got stuck. I obviously made a mistake somewhere, does anyone have any ideas how to unbrick my phone. Not too make it sound worse but I have to use my wife's old Blackberry...a pink flip!
Linux works better. After dl, right click, permissions, check the little box that says make it executable. Click ok. Now right click on it, open with java (either open jdk, or sun java ). The app should open.
Thanks very much, I was now able to install on Linux but after all this the unbrick did not work. It tells me to plug my phone in, the phone is in the USB port it has always been in. I turned the phone in the off position and all it does is show a load symbol similar to the one before the battery charge comes on, when it goes on it just stops at the i896 screen and does nothing else. Any other ideas on how to unbrick this phone? or am I done and got to get a new one? I'd rather keep this one
Ok not to say nothing is working, but I have a yellow triangle with Android digging, says downloading below and at the bottom do not turn off target!!! What does this mean?
coltiger said:
Ok not to say nothing is working, but I have a yellow triangle with Android digging, says downloading below and at the bottom do not turn off target!!! What does this mean?
Click to expand...
Click to collapse
Plug it into the computer and hit the button.
I tried that but my pc doesnt pickup my Samsung anymore, it is like it doesnt exist when I plug in. I am gonna reboot the PC and retry.
Are you using a Linux machine?
yes I am I have Ubuntu 11.10 installed, I never had this trouble before with it recognizing the phone.
If you can get download mode, flash back to stock.
It goes into download mode but not sure how to flash to stock
There is a sticky in the development section for stock ROM.
http://forum.xda-developers.com/showthread.php?t=1285616
Thanks guys, I have read the instructions and all is fine except that I am using Rogers version i896, if it doesn't make any difference then I will load the AT&T if there would be issues. Second issue I am running into is while my phone goes into download mode, my PC's continue to not see my phone, I have removed everything including the SD card. Any ideas how to get the phone to be recognized as I think this would solve a lot
My friend recently had similar problems and it turned out to be a bad cable. Don't overlook the obvious.
/e
Sent from my SGH-I897 using xda premium
EDIT: I FINALLY GOT ADAM OUTLERS HEIMDALL 2.2 ROM TO INSTALL.
---------------------------------------------------------------------
So I was running 4.2.2 SlimBean on my Girlfriends phone.
But found out the phone needs to be unlocked.
Then found out you can't unlock a 4.2.2 phone based on AOSP.
So I've been trying like crazy to downgrade to a Froyo or GB ROM so I can unlock phone.
But NOTHING is working.
The odin-one-click's don't work.
The Adam Outler Heimdall just keeps saying there are no drivers for Heimdall, then installs drivers succesfully, then says there are no drivers...
Any Froyo or GB ROM I flash in CWM 6.x.x or older, just gets to boot screen and won't go any further.
I'm flipping annoyed here. Help!
My googling has worn my fingers numb and I gotta have someone take pity on me and tell me what the frack to do.
I've soft bricked this phone about fifteen times so far. The dang "computer & phone" screen thing has been kicking my butt over and over. Glad I finally got a fix for that. But, I keep bricking the phone again afterwards. ugh...
HOW THE HECK DO I GO ABOUT DOWNGRADING THIS PHONE ?!?
CZ Eddie said:
The odin-one-click's don't work.
Click to expand...
Click to collapse
I use Win 7 computer, original Samsung USB cable, correct drivers + run Odin one-click as Administrator and it works perfectly every time. Had to go back to stock GB a few times, no issues.
Well I don't know what combo of driver & kernel & other stuff worked, but I finally got the Odin One Click thing working. Not all of them work, but I found one that did (I897UCKF1_withBL). Even then, it only works about 1/2 of the time.
Flashed a 2.3.3
But after rooting it, I lost WiFi ability.
And so couldn't unlock it.
And this forum is full of DEAD links for everything I need that is old enough to unlock a phone.
awwrrghhh I'm ready to throw this phone against the wall.
AT&T already gave me the code to unlock it. And I have a new unused AT&T SIM installed, though it sounds like that may be a problem also. I might need a non-AT&T SIM to unlock.
Q&A for [GUIDE]How To Unbrick Your Galaxy Tab!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE]How To Unbrick Your Galaxy Tab!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Galaxy Tab 3 T210R / Bricked?
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Bricked, or not bricked? Samsung Galaxy T210R
gtcreative said:
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
___________________________________________
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Click to expand...
Click to collapse
____________________________________________
Update 07/07/2015
I let the tablet's battery run down (as was suggested in one of the threads), and when I plugged it in to the AC power, I got the Samsung Galaxy logo!
I was then able to restart in download mode, and reinstall the md5 file via Odin. Not sure why letting the battery run down works, but at this point, I don't really care. I'm glad that the tablet could be resurrected from the dead, in spite of my mistake.
I hope this is helpful! :victory:
tab not showing up in ODIN
I have my galaxy tab soft bricked, but when I plug it in to ODIN, the pc does not recognise the tablet and therefore I can't reinstall the firmware, although the tablet is connected to the pc, as it gets charging when plugged in.
I've tried reinstalling samsung drivers, killing every samsung keys program running in background, another cable and even three different ODIN versions (v.1.7 // v3.07 // v.3.09), but it is not showing up in any version.
I have been looking for a solution since last year. last year I had windows 8 and it didn't work; then I upgraded to win 8.1. again nothing, and with windows 10 the same story. can anyone help me please?
thank you very much.
internal memory read only my p3100
hi ..
thanks in advance
i dont know what happened to my tab p3100, i am not able place any files in internal memory.
it will get into the main screen and gives bunch of errors like process google play is not working... bla bla bla...
i can uninstal the function but after reboot it will be there in the phone. i am bit tensed what is this is this a bricked one or?
please help me out i tried odin, through odin i installed omia rom 5.1 after that this error i am getting please help me out to solve this.
my phone already rooted..
Once again thanks hooping for the fix.
please mail the fix to [email protected]