Related
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
Early yesterday I launched Kies and hit the update firmware option from the tools menu to see if the alleged ICS update was available for my phone. It appeared it was with, a message promoting that it would clear all personal data from the phone, which I then selected cancel so I could do a backup of pictures/videos on the phones internal SD.
Without doing any sort of backup yet I shutdown the phone, only for it to freeze on the shutting down screen. After 20 mins I pulled the battery and let the phone cool down since it had gotten warm trying to shut itself down. After replacing the battery and turning on it was stuck in a bootloop with only the SGS2 logo, never reaching the ATT logo.
At that point I came to XDA, which I frequently browse but have yet to root, and began reading and searching everything I could find.
Hours later I decided to attempt to flash the stock firmware from sammobile.com using Odin. The flash took a long time and I assume never completed. I left it overnight since I didnt want to unplug it mid-flash. Checking back in the morning the phone is black, Odin says failed/disconnected, and I find the battery completely drained. I charged it for a while then tried turning it back on and got the yellow triangle "firmware upgrade encountered an issue..." screen.
Now i'm attempting once more to flash the firmware but again it has been 30 mins on Sbl.bin. I've had a hard time finding stock firmware in different varieties with working links, so to not increase the flash counter in the event I ultimately have to send it in for repair.
Any suggestions on where to go from here? I've followed every direction I can find for flashing stock firmware and nothing has been successful.
Glad to help if I can. Please tell me exactly what package you flashed from sammobile, with a link if possible.
You should change the title of the thread.... I killed my phone. LOL!
http://forum.xda-developers.com/showthread.php?t=1313659
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
Try this.....
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
Download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package from Hotfile. Extract the contents of the zip file to a directory on your hard disk drive. This is a One-Click version of Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package plus stock modem from the development forum. (Contains stock zImage, factoryfs.img with root, and modem.bin.)
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD With Root.exe".
Now Enter Download Mode:
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.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success. You're Rooted.
SOURCE: http://forum.xda-developers.com/showthread.php?t=1311081
creepyncrawly would know better. It's his thread.
Download the file from below post to go back to stock I777UCKH7. Follow the instruction written in the post. I just had the same a while ago using the mobile odin to go back to stock. Got stuck on Samsung Galaxy SII screen. Pulled the battery and then followed the instructions from this post. I selected the one that says no BL 'I777UCKH7 OCD No BL'.
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
Once you are done with the stock restore. To upgrade to ICS LE5 follow the instructions from below post. Make sure you read and follow the instructions as mentioned in the post.
http://forum.xda-developers.com/showpost.php?p=27707563&postcount=83
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
You downloaded I777UCKH7_I777ATTKH7_ATT and extracted I777UCKH7-rev02-home-low-cl503881.tar.md5?
Flashed the .tar.md5 in the pda slot?
What version of Odin are you using?
Edit: You're getting lots of advice here. Let me know if you need me to help troubleshoot your issues.
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
nett3 said:
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
Click to expand...
Click to collapse
Try using another micro usb wire if you have one. If not then get one from radioshack or bestbuy. I had the almost similar issue on my captivate with the original USB cable. Then I got a Rocketfish one from bestbuy and it worked like a charm.
I'm sure you might have already done this. Make sure you first run the ODIN and then put your phone in download mode.
krips your a genius!
The one click is now working thanks to the suggestion to pay attention to order of operations. I must have never plugged the phone in AFTER starting the one click. This was easily overlooked when I've been switching the phone between 2 PCs and 3 micro usb cables.
I now have a progress bar and have had made more progress than in the last 24 hours. Even after searching I did not find this solution, even though it's stated in the directions and it seems trivial, maybe it should be emphasized the one click needs to phone plugged in after it's running.
Thanks again. I'll update this post when it's back to being a phone again.
PS. BROKKANIC: you were right, if I didn't kill my phone then I sure was the impeding factor in its recovery.
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Is this a bootloader problem, kernel problem, or something else?
LOL!. Glad you got it working.
nett3 said:
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Click to expand...
Click to collapse
Flash back to stock first.
BROKKANIC said:
LOL!. Glad you got it working.
Flash back to stock first.
Click to expand...
Click to collapse
I believe that what I have been doing. I ran I777UCKH7 OCD With Root.exe, which resulted in bootloop, then ran I777UCKH7-CL503881-No-BL.exe, which also resulted in bootloop. Both completed successfully, but resulted in the same bootloop.
Odin appears unable to flash anything without it being a one click. I'm trying to flash Siyah-v2.6.14-att.tar. But Odin hangs at zImage with no progress bar.
What operating system you using: if windows 7 are you running as administrator ?
hd779 said:
What operating system you using: if windows 7 are you running as administrator ?
Click to expand...
Click to collapse
I've resorted to my WinXP laptop which has been more successful than my Win7 desktop. On the Win7 attempts everything is run as admin, but has many time bluescreened and hard reset the whole PC when attempting to flash anything with Odin. Maybe a separate issue, maybe not. But the XP machine is atleast successfully flashing the Odin one clicks.
Update: Odin standalone (non-one click) appears to be unable to flash anything, it will only hang when trying to write. One click Oden packages seem to work. Is there a one click with full stock sbl, param, kernel, etc?
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
gefox4vn said:
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
Click to expand...
Click to collapse
I haven't flashed a package with a bootloader yet. The only ones that work for me are Odin one click packages, and the two I've tried do not have bootloaders. I've been looking for one WITH a bootloader but no such luck yet, since maybe that would solve the problem.
The guide/link you've suggested will not work for me at this time. I do not have the ability to boot into any andriod OS. The only capability my phone has is executing Odin one click packages for some reason, even Oden standalone firmware flashes do not work.
I had a similar issue...I eventually got mine stuck at the ATT droplets....
Finally I flashed back to 2.3.4 stock....did the ota...then upgraded to ICS.
Its all on my work laptop so I wont be able to post any specific files or their names until monday...
Good luck!
Once your phone gets to the boot screen try to get into stock 3e (both volume buttons + power till 2nd SGSII splash screen) recovery and do a factory reset. Should boot after that. Good luck.
Sent from my SAMSUNG-SGH-I777 using xda premium
Why not try a custom ics rom? What else do you have to lose? Staying stock is overrated anyways. You may also have an antivirus stopping Odin but I doubt it. Just turn off your antivirus and try.
Sent from my SGH-I777 using xda premium
Alright, so here's my problem:
I just upgraded to the Galaxy S III yesterday, and today decided to try to 'root' the device. So I found the Toolkit here on XDA (from here), and went through the initial steps without any issues (driver installation, device recognition, etc..).
I then went to the 'rooting option' menu, where I selected the first--and most basic --option, which was to only install Super User, and the push the permissions.
I was following the automated guide, opened Odin, selected the correct file, 'boot-insecure-i9300xxale8-gsm.tar', and made sure only 'auto-restart' and F.reset time' were checked, and clicked 'start'. The flash appeared to have gone well, but when it tried to restart, the phone never rebooted. I attempted to reboot into download mode (Vol. Down + Home + Power), but the device was unresponsive. I then browsed around the forums a bit looking for other methods, including taking the battery out for several minutes, then putting it back in whilst holding down the 'download mode' button combination, and other various variations of that method; yet again, none prevailed.
The device gives no indicator lights when plugged in, no light up when the power button is held down, and is overall seemingly unresponsive. However, when I hold down the 'home' button alone - after about 30 seconds - a green vertical battery appears on the screen, with a little white loading indicator on it, but vanishes after about 5 seconds or so, and the device becomes unresponsive once more.
The device is not being recognized by my computer whatsoever, no beeps or anything when plugged in.
Any ideas as to what I can do?
EDIT: I have been able to get into 'Download mode' somehow, but after trying to reflash the stock rom, it went back to the 'Unresponsive' mode. I have it in Download mode again currently, so what do I do from here?
I assume it is still under warranty, since it is less than a few days old. Return it to the store claiming hardware malfunctioning.
Forget about the toolkit. In my opinion, it's quite useless (as you know by now), and it tends to automate tasks that are simple by nature.
Even although I appreciate the effort the developers of the toolkit put into it, I would never do it, since I want to have control of the entire process: I want to know exactly what is being done and why, and that is something the Toolkit won't give me.
If you want to root your phone and keep it stock, do this:
- Install the drivers for the device.
- Install SiyahKernel for S3 version 1.3 using ODIN.
- Install superSU (from market) and let it update it's binary su
- Install MobileOdin (free version)
- download the latest Samsung ROM (such as DBT [Germany] or ITV [Italy]) using CheckFus downloader
- copy the downloaded and unzipped ROM to your phone's external SD card (just the .md5 file)
- using MobileODIN, flash the ROM and select the "EverRoot" feature
- after reboot the ROM will be updated, stock, but with root
- Install TriangleAway to get rid of any annoying triangles and to reset the binary counter
Done. supposing the ROM is already downloaded, the entire process takes exactly 4 minutes.
Simonetti2011 said:
I assume it is still under warranty, since it is less than a few days old. Return it to the store claiming hardware malfunctioning.
Forget about the toolkit. In my opinion, it's quite useless (as you know by now), and it tends to automate tasks that are simple by nature.
Even although I appreciate the effort the developers of the toolkit put into it, I would never do it, since I want to have control of the entire process: I want to know exactly what is being done and why, and that is something the Toolkit won't give me.
If you want to root your phone and keep it stock, do this:
- Install the drivers for the device.
- Install SiyahKernel for S3 version 1.3 using ODIN.
- Install superSU (from market) and let it update it's binary su
- Install MobileOdin (free version)
- download the latest Samsung ROM (such as DBT [Germany] or ITV [Italy]) using CheckFus downloader
- copy the downloaded and unzipped ROM to your phone's external SD card (just the .md5 file)
- using MobileODIN, flash the ROM and select the "EverRoot" feature
- after reboot the ROM will be updated, stock, but with root
- Install TriangleAway to get rid of any annoying triangles and to reset the binary counter
Done. supposing the ROM is already downloaded, the entire process takes exactly 4 minutes.
Click to expand...
Click to collapse
Thank you so much for responding!
I have the phone in download mode right now though, as I've been able to get that far. Is there anything I can do from here to fix the issue? I really don't want to take it back up, and face the chance of confrontation if they decided to call me out on the issue.
I tried flashing the Sinyah Kernel via Odin just now, using the PDA mode, but once again, just flashes the Samsung logo for a brief second, and disappears, leaving me with a black screen.
Samsung don't seem to really care if you have rooted or not, so far about 4 people in 2 days on this and other for mums have returned phones because they have possibly bricked them, all got them exchanged with out a problem.
To unroot and return your galaxy S3 to stock for warranty watch this. http://www.youtube.com/watch?v=_8Tga_yKywc&feature=youtube_gdata_player
Zenno said:
Thank you so much for responding!
I have the phone in download mode right now though, as I've been able to get that far. Is there anything I can do from here to fix the issue? I really don't want to take it back up, and face the chance of confrontation if they decided to call me out on the issue.
I tried flashing the Sinyah Kernel via Odin just now, using the PDA mode, but once again, just flashes the Samsung logo for a brief second, and disappears, leaving me with a black screen.
Click to expand...
Click to collapse
Flash a stock rom for your phone and location or if it was a branded phone flash that .
Even if it does not boot you stand a better chance under warranty .
Say you where doing a Kies update and it just failed to reboot .
jje
JJEgan said:
Flash a stock rom for your phone and location or if it was a branded phone flash that .
Even if it does not boot you stand a better chance under warranty .
Say you where doing a Kies update and it just failed to reboot .
jje
Click to expand...
Click to collapse
I tried to reboot the stock firmware 'boot-stock-i9300xxale8-gsm.tar', but when Odin failed to reboot the phone, and I manually put it back into download mode, it still said my binary was 'Custom'.
Should I be trying to flash that under 'Bootloader' in Odin or something? Because I've been doing 'PDA' and it hasn't been working.
Download an original, stock ROM from samsung-updates.com or use checkFus downloader.
That is what you'll flash.
This is the one I use: http://samsung-updates.com/get/1932/Samsung_Firmware_GT-I9300_DBT_I9300XXALF6_Android_4_0_4.html
After some further browsing, I was able to fix it thanks to this post here, posted by 'mskip'.
Whew! That was stressing. Thanks guys for helping out though!
How to get out of hard brick to download mode
Zenno said:
After some further browsing, I was able to fix it thanks to this post here, posted by 'mskip'.
Whew! That was stressing. Thanks guys for helping out though!
Click to expand...
Click to collapse
After hardware brick, how did you get it back to download mode agian?
i cnat do anything , no turn on no charging, nothing, how you do it?
i think if i can get it back to dowload mode, i can flash out the stock rom again.
any advise will help
Pull the Batteery
jiafu790617 said:
After hardware brick, how did you get it back to download mode agian?
i cnat do anything , no turn on no charging, nothing, how you do it?
i think if i can get it back to dowload mode, i can flash out the stock rom again.
any advise will help
Click to expand...
Click to collapse
Remove the battery for about 2 minutes, replace it and immediately try to go into download mode. This worked for me
same problem
Hard bricked it too, flashed a wrong rom made for international model, i have the att model are you sure taking out the battery works?
Zenno said:
EDIT: I have been able to get into 'Download mode' somehow, but after trying to reflash the stock rom, it went back to the 'Unresponsive' mode. I have it in Download mode again currently, so what do I do from here?
Click to expand...
Click to collapse
I have the same problem! Do you know how you got into download mode?
Surge411 said:
I have the same problem! Do you know how you got into download mode?
Click to expand...
Click to collapse
Just keep trying,I must have removed the battery and pressed the buttons over six times to get into download mode. Hope you get there.
So my girlfriend's Verizon Galaxy S III is in quite the jam. The power button stopped working. She has to use a software button to turn the screen off and the home key to turn it back on.
Verizon sent over a replacement, but she needs to send the original phone in. Problem is, the normal methods for returning to stock all involve Odin, which requires the phone to enter Download mode....which we can't do. The phone won't register the power button being held down. I don't even want to turn it off since I'm not sure it could be turned back on.
So I've been googling around for another way (already having used Triangle Away) and found a couple of sets of instructions (here and here) on using Odin Mobile to flash the phone back to stock. But there seem to be a lot of comments around, especially on the YouTube video guides, of people saying it bricked their phone.
What's the safest bet here? As far as I can tell these are the options:
-Shut down the phone and pray the power button somehow works for getting into download mode (doubtful) so I can use Odin.
-Restore a nandroid / flash a zip of the stock ROM and then use EZ Root or whatever to unroot the phone and hope Verizon doesn't look into it.
-Use one of these sets of instructions for Mobile Odin...though it's not clear which one is best and what files I should be using.
-Just send it in and pray.
Odin Mobile seems like the smartest option...but the instructions out there aren't as comprehensive and up to date as I'd like. I'd rather not brick the phone.
Can anyone help? The phone is currently on AOKP 4.2 Milestone.
theEastonator said:
So my girlfriend's Verizon Galaxy S III is in quite the jam. The power button stopped working. She has to use a software button to turn the screen off and the home key to turn it back on.
Verizon sent over a replacement, but she needs to send the original phone in. Problem is, the normal methods for returning to stock all involve Odin, which requires the phone to enter Download mode....which we can't do. The phone won't register the power button being held down. I don't even want to turn it off since I'm not sure it could be turned back on.
So I've been googling around for another way (already having used Triangle Away) and found a couple of sets of instructions (here and here) on using Odin Mobile to flash the phone back to stock. But there seem to be a lot of comments around, especially on the YouTube video guides, of people saying it bricked their phone.
What's the safest bet here? As far as I can tell these are the options:
-Shut down the phone and pray the power button somehow works for getting into download mode (doubtful) so I can use Odin.
-Restore a nandroid / flash a zip of the stock ROM and then use EZ Root or whatever to unroot the phone and hope Verizon doesn't look into it.
-Use one of these sets of instructions for Mobile Odin...though it's not clear which one is best and what files I should be using.
-Just send it in and pray.
Odin Mobile seems like the smartest option...but the instructions out there aren't as comprehensive and up to date as I'd like. I'd rather not brick the phone.
Can anyone help? The phone is currently on AOKP 4.2 Milestone.
Click to expand...
Click to collapse
wrong section buddy. this is international gs3 forum! here's where you have to go : http://forum.xda-developers.com/forumdisplay.php?f=1708
Answer has nothing to do with phone model.
Mobile Odin is the best option you have. I've never used it for a whole Rom. Install mobile Odin + its kernel flash add on (specific for phone model, it's well guided) then I guess you download a whole Sammy Rom in tar format.
Then in mobile Odin use Open File option file in menu.
I guess there must be some guides to confirm that.
Thanks for the response! Didn't realize I was in the wrong section. I'll post over there to see if people have recommendations for which files I use.
you can reboot into download via adb.
it's something like "reboot bootloader", use search.
Hello forum people, I need help to revive my S3 i9300, if you could help me I would really appreciate it.
I tell what I remember about the problem:
The phone was rooteado to be able to use it with any company since it was of movistar. a year ago with the rootking (we sent it to root), the phone was my dad and now has a new one, and it stopped using about 2-3 months.
Then I lent it to a friend who had just broken his cell, so I gave it to him so he has something until he buys one, but he told me that it did not work because he did not load and unload very quickly. He gave it back to me and I stopped using it until about 1 month ago, that I was left without a cell phone and I want to use it to have something.
The same thing happens as it does not load and it is very easy to download, BUT if you use the charger and cable of the Huawei ascend Mate 7 that my dad has, it charges perfectly and the cargo is not cut at all.
Well, seeing that this happened, I restarted it from the factory (I guess the root will be removed with that).
It was still branded and only loaded with the charger and the Huawei cable ...
Well now I tell what happened with what I did.
I install the samsung drivers for the compu, install odin 3.10.6 and under the recovery file that I put up, well I install everything but when I realized instead I read fast and instead of saying PDA said AP in the odin.
Well I try to turn it on and it does not turn on, I try to enter into recovery mode and it does not start.
Then I install another odin, version 1.30 and have a PDA, I do everything as I say start the phone in download mode, home odin, connect the phone to the computer, put the file in pda and give start.
He tells me that everything went well but still does not turn on and without going into recovery mode.
Say that when I do recovery mode (volume up, home and power) I see the logo of samsung and like that desinstegra, then it appears again and blinks in blue but as if it were broken and the logo moves. In short broken.
Then then install another recovery, https://dl.twrp.me/i9300/twrp-3.0.2-...0.img.tar.html
Now I want to enter into recovery mode but this appears and I want to touch some option that appears but nothing, as if the touch was dead.
And after that, it seems to me that I tried to change the Kernel and I put any but the one of my model by mistake.
Current status of the s3:
It lights normally but it takes a long time.
Enter DOWNLOAD mode (vol down, home and Power)
The screen touch does not work but it does show an image.
The buttons work, also the easy button of back and home.
DO NOT enter RECOVER mode (vol up, home and power) is frozen in the Samsung logo.
I want to make it work with any other rom that is functional except the STOCK. And that transforms into unlocekd
It does not matter if when I install a new ROM the files are deleted, I do not have anything in the phone.
Thank you very much to those who respond.
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
rodman01 said:
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
Click to expand...
Click to collapse
Hello, if I think that the Kernel had changed I do not remember exactly what it was because I downloaded it on a page written in Asian language by mistake and the Google translator confused the words and he said it was from the s3 but I think it was from the note 3.
The tactile does not respond exactly.
I did not understand him completely, he wants me to enter RECOVERY mode (it takes about 15-20 min to enter) and then do a factory reset?
I almost forgot to clarify that I had tried to do this from the video: https://www.youtube.com/watch?v=fA86_HFGx_w
Everything was installed perfect and I did it as is, except to delete.
Or reinstall the factory rom to see if it worked again.
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
rodman01 said:
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
Click to expand...
Click to collapse
Could you tell me how to do it please? I'm not an expert at all in changing ROM.
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Edit: for example:
https://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 and from there for example
https://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
rodman01 said:
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Click to expand...
Click to collapse
I used odin but I forgot how I had done and had followed the steps of a tutorial that I lost the link.
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
rodman01 said:
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
Click to expand...
Click to collapse
Hello, thank you very much for the links that you have passed me. They will be very useful, excuse me but I do not want to be irritating at all but I am really lost.
My only question is to know how to start reliving it?
I start installing CWN and then change the ROM?
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
rodman01 said:
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
Click to expand...
Click to collapse
Hello, I did the following, I had tried to re-install the stock stock a few days ago and it did not work, I did it for odin.
So what I did today was, install the recovery mode of ClockWorkMod and probe with the rom of MIUI 8 and that of Linage16, no installation. Then try with this: https://forum.xda-developers.com/galaxy-s3/development/rom-t3442868 And install correctly but it does not work, pass the Samsung logo but then when the ROM logo appears it stays there frozen and restarts ... it seems to me that officially the phone is dead.
Again: the right stock samsung sw should work if flash via odin didn't fail and, what I already mentioned, after flashing you did a factory reset in recovery. After that the reboot into system could take several minutes. Otherwise you can try it with repartition efs backup restore etc etc etc.
btw: newer custom roms, like leo-16, cannot be flashed with the old cwm recovery and cwm touch recovery, as you mentioned in the related thread, would not make much sense, if your touch is broken!?! If you do not want to go via samsung stock sw, then get a newer twrp, search for info which one is suitable, and guides how to flash custom roms, and flash the preferred one of your choice.