Related
Hello ppl,
i got a big problem, i hope someone can help me.
A friend of mine, gave me his galaxy s 2 to fix it. It just showed the battery icon with a circle running into it.
I fixed it with the JIG and got into download mode.
Everything is fine until now, even the flash with Odin shows success, but the phone just wont start up.
It doesnt matter what i do, or flash, its stuck in the samsung galaxy s II screen.
Download Mode is working, but Recovery not. When i try to enter the recovery mode, the phone hangs with the same screen like above.
Is there anything i could try to fix this?
Thank you
geminga
Okay relax, as you can get into download mode, there's a chance that you can still fix it.
I think you're running the wrong kernel or modem here.
I advice you to freshly install a new rom, and then install a CF-Rooted kernel that allows you to get back into recovery.
Once you got that worked out, get into recovery and select Wipe/factory reset. It should boot now.
If this still does not solve your problem, install VillainRom 2.0 using the process described in the thread. I had the bootloop problem too, but Wiping, Flashing and Wiping again did the trick for me.
Thank you mate I will try this later. Im will report if I was successful. (i hope so)
I flashed 2.3.4 ROM with Odin and then CF-Recovery but i can still not access recovery mode. It shows the yellow triangel but still hangs with the samsung galaxy screen.
I think that phone has become a nice paperweight...
As 2.3.4 is a test release i would try older stable firmware .
Flash a stock 2,3,3 rom via Odin and see if it boots .
jje
Is there something for Samsung that completely replaces everything including ROM,recovery and such things?
From my desire I know, if a RUU can't boot your phone it is 100% bricked. So I need something like that for that sgs2, to be sure that this is no hardware failure...
I will try some flashes and report after that.
Sent from my HTC Pyramid using XDA App
what i would do is install one of these carrier branded ROMs http://forum.xda-developers.com/showthread.php?t=1113928
and see if it boots, if it does then flash the cfroot [specific to the carrier version you choose e.g. KF2] make sure thats the right one. that should give you recovery as prodygee has said. then do a full wipe, system, data, cache, dalvik and reboot.
afaik this should work. that's worked for me on numerous bootloops!
Hope this helps, Rumble
solved [Arrow Galaxy s 2 wont start]
i just followed this link... >>1.Make sure that your phone is Samsung Galaxy S2 not any other.If you try this process on any other phone then the phone will be damaged.
2.Create a backup of your all useful phone data with the help of backup apps that ensure your phone data.
3.This process will take several minutes or may be hours so make sure that your phone battery consumption is maximum.
4.Remove the SIM card and external storage SD card.
5.Download both these files.
Download Gingerbread 2.3.4 XXKGI Firmware
Odin3 v 1.83
Procedure for Update Samsung Galaxy S2 GT I9100 to Gingerbread XXKG1 2.3.4 Firmware.
1. Open the Odin.exe file you will see the window image on your screen.
2. Switch off your phone then press and hold the Volume Button with the Power Key and HOME to turn the phone into the download mode.
3. Now connect your phone via USB cable to the computer. After connectivity you will see the window screen in which you see the COM ID 5 as a yellow color.
4. Now add the following files in the corresponding options:
PIT – u1_02_20110310_emmc_EXT4.pit
PDA – CODE_I9100XXKG1_CL349526_REV02_user_low_ship.tar
Phone – MODEM_I9100XXKG1_REV_02_CL1034110.tar
CSC- GT-I9100-CSC-MULTI-OXAKG1.tar
5. Click on the "Start button". Then updation process is start and wait for some time.Please don't interrupt your device will installation.
6. When the installation is completed reboot your phone and remove cable connectivity.The previous version of this firmware is also stored in cache memory.Remove your previous firmware version by dialing*2767*3855#.Now Update and check the latest version by dialing *#1234#.
it worked perfectly for me
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
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.
Hi,
BeforeI begin I would like to state the I have searched the forum for solutions but the ones i findthe person can get into DL mode the only one that is just like my issue doesnt show how ODIN worked for him. but anywho...
I have a Glaxy SGH-I717 and it is stuck at the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN."
How this started was I newly installed Kies and tried to back it up, but by mistake started to upgrade it. not wanting to mess up the phone I let it run without the phone being in download mode. after a bit the upgrade failed and my phone was stuck at the error message screen above. to reboot the phone i have to remove the battery. pressing the button on turns it off but back on at the error screen. my computer makes the sound like it recognizes the phone but doenst show it in my computer. Kies just says connecting for awhile then stops.
Things I cant do with the phone
- get into download mode - when trying it goes the the press up or down button (ethier one goes to error screen)
- get into recovery mode - the samsung logo flashes for a second then goes to the error screen
things i have tried
- Using oding to flash ROM(tried two different files both from da_g for flashes)
each time odin states it failes at the write stage
- Kies emergency recovery (it freezes at 0% somtimes it says the phone is disconnected)
- Used one click fix program (made me click more then once)
I'am curently looking into trying the adb solution usind android sdk. just making the post here to see if anyone knew a easier solution to this.
Fixed
Problem is fixed, switched USB ports and found a different ROM to flash in ODIN. I now see why people love ODIN better then Kies
heelllp
Rremann1 said:
Problem is fixed, switched USB ports and found a different ROM to flash in ODIN. I now see why people love ODIN better then Kies
Click to expand...
Click to collapse
what ROM did you use? where can I find it? I have the same problem you had, except I was only trying to hard reset the sgh-i717 but the only option I could seem to get to was "A custom OS can cause critical problems in phone and installed applications. If you want to download a custom OS, press the volume up key......" etc This is my friends phone I was just trying to hard reset it because she forgot her pattern lock, so I downloaded a ROM and odin and when I attempted to flash it, it got to that error screen you had. It lets me get back to the previous screen but always goes back to firmware upgrade issue screen no matter if i choose up or down. :crying: I have flashed a couple phones before by following tutorials on the web. I though it was only giving me that option because the phone might have already been rooted, it never let me go to the wipe data menu. The instructions all said to hold volume up + home + power, it never did anything for me. I was only able to get to the custom OS screen by holding volume down and power button. you were able to get back to the ready to flash screen? Tried taking out the battery and turning off with power button always goes back to Firmware upgrade encountered. Please help if you can, if I am breaking some forum rules sorry! just need help! Am running windows xp, since the phone was loccked have no idea what it was running, just that its an att samsung galaxy note sgh-i717. it saysin odin mode, custom binary download: no, current binary : samsung official.
thank you!
---------- Post added at 10:50 PM ---------- Previous post was at 10:03 PM ----------
tech_girl85 said:
what ROM did you use? where can I find it? I have the same problem you had, except I was only trying to hard reset the sgh-i717 but the only option I could seem to get to was "A custom OS can cause critical problems in phone and installed applications. If you want to download a custom OS, press the volume up key......" etc This is my friends phone I was just trying to hard reset it because she forgot her pattern lock, so I downloaded a ROM and odin and when I attempted to flash it, it got to that error screen you had. It lets me get back to the previous screen but always goes back to firmware upgrade issue screen no matter if i choose up or down. :crying: I have flashed a couple phones before by following tutorials on the web. I though it was only giving me that option because the phone might have already been rooted, it never let me go to the wipe data menu. The instructions all said to hold volume up + home + power, it never did anything for me. I was only able to get to the custom OS screen by holding volume down and power button. you were able to get back to the ready to flash screen? Tried taking out the battery and turning off with power button always goes back to Firmware upgrade encountered. Please help if you can, if I am breaking some forum rules sorry! just need help! Am running windows xp, since the phone was loccked have no idea what it was running, just that its an att samsung galaxy note sgh-i717. it saysin odin mode, custom binary download: no, current binary : samsung official.
thank you!
Click to expand...
Click to collapse
I have read several forums searching for answers, no one ever stated that odin will still work while on the screen that said "Firmware upgrade encountered an issue..." pretty positive it flashed the lock screen background and the user settings that were on the lock screen are no longer there it had said something to the effect of " ____ password protected!" ill leave the blank up to your imagination. The user settings are gone but not the pattern lock! all I want to do is hard reset to eliminate the lock pattern lock???
Thanks
ROM Link
tech_girl85 said:
what ROM did you use? where can I find it? I have the same problem you had, except I was only trying to hard reset the sgh-i717 but the only option I could seem to get to was "A custom OS can cause critical problems in phone and installed applications. If you want to download a custom OS, press the volume up key......" etc This is my friends phone I was just trying to hard reset it because she forgot her pattern lock, so I downloaded a ROM and odin and when I attempted to flash it, it got to that error screen you had. It lets me get back to the previous screen but always goes back to firmware upgrade issue screen no matter if i choose up or down. :crying: I have flashed a couple phones before by following tutorials on the web. I though it was only giving me that option because the phone might have already been rooted, it never let me go to the wipe data menu. The instructions all said to hold volume up + home + power, it never did anything for me. I was only able to get to the custom OS screen by holding volume down and power button. you were able to get back to the ready to flash screen? Tried taking out the battery and turning off with power button always goes back to Firmware upgrade encountered. Please help if you can, if I am breaking some forum rules sorry! just need help! Am running windows xp, since the phone was loccked have no idea what it was running, just that its an att samsung galaxy note sgh-i717. it saysin odin mode, custom binary download: no, current binary : samsung official.
thank you!
---------- Post added at 10:50 PM ---------- Previous post was at 10:03 PM ----------
I have read several forums searching for answers, no one ever stated that odin will still work while on the screen that said "Firmware upgrade encountered an issue..." pretty positive it flashed the lock screen background and the user settings that were on the lock screen are no longer there it had said something to the effect of " ____ password protected!" ill leave the blank up to your imagination. The user settings are gone but not the pattern lock! all I want to do is hard reset to eliminate the lock pattern lock???
Thanks
Click to expand...
Click to collapse
Hi I am sorry if this is hard to read i' am a little bit ____ ill leave the blanks up to your imagination. below is the link to where u can use the rom i used. and yes you can run odin on the error screen.
go to this site download pdr.tar there's a link for odin as well. GL
Hope this helps ^^
Sorry to rez such an old post but i broke screen on my current phone and needing another phone asap I ventured into the big bin labeled Misc Phone Parts and all i could find (screen came on)was my old Note. Popped in in Sim using an adapter.
And thought i was good until I saw Phone icon dots Yellow triangle dots PC monitor. Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again.
After about 6 hours I do not have it working. I am not new to samsung flashing having flashed my first phone 4 years ago and since then installed 30 plus custom ROMS on all my Galaxy phones through out the years. Sure I can just find used much better phone but then this will not be resolved and will keep me up at night. (if your like this you know what I am talking about).
So back on XDA where I am thankful and appreciate all the members who have contributed helpful information that has saved this world from filling with an ocean of frustration. Myself being one of those who has been saved many times by reading and following directions of what others have done. I like to think that a persons efforts to help someone last well beyond their own lifetime. Thank you sir or miss (yes you) for the work done selflessly with out recognition and reward that continues to help make the lives of others who they may never meet or know better and more happy.
Is my Samsung Galaxy Note 2 Bricked ?
I got the phone from Ebay on July 6,2015 everything was great
But on the morning of Sep 21st looking at my gallery pictures, I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right the phone restated saying "Samsung's firmware upgrade encountered an issue" so the next day did some research first before trying anything. I downloaded Odin3 and entered download mode & flashed the Samsung it restarted had it on for 3-4 hours
then turned it off & turned it on later to find it would not go pass the Samsung logo so I went to hold the off button shutting the phone off that happen 2 times and on the 3rd try turning it on It did not come on at all. Went to see if google had anything on this some say it is bricked and need to use a jig so I got one from a USA seller on ebay and returned it because it did not work at all. Not the phone still won't come on & I can't enter download mode, how do I fix this, is it a boot loader problem? is it hard bricked? do I need to take it to someone if so who & how much would that cost? you think.
Other Info of the phone
70% of battery is on the phone
It's factory Unlocked
Root Software I tried to use was (Kingo SuperUser)[Root]
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
dseldown said:
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
Click to expand...
Click to collapse
Should I post this in the Troubleshooting Forum?
The pictures I took on the phone disappeared all 300+ pictures disappeared .I am the only one using the Samsung
and it was on my table all that day. So I went to google to find a photo recovery software & found a software called
Wondershare Dr.Fone for Android (you can find videos on youtube) & using the software it can do 2 things, auto root the phone to find the photos and bring it back to normal or you Have to have your phone rooted. The auto root setting was not working on the Wondershare Dr.Fone for Android software so I went to the google play store on my Samsung and found a root app that a lot seem to like as it was 4.4 stars, went to install that the app stated I should have "Kingo SuperUser" on my computer so had that put on the went to root the phone & it did not work.
I got a screen on the Samsung saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Youtube had a video on this same problem so I went to Sammobile's site and download the firmware what was
"2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies. After I downloaded that I downloaded Odin3_v3.10.6 opened it had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion then Entered Download mode on the Samsung & hooked it up to my computer
then I hit start about 30min later it Passed with a green light and everything seem back to normal 3 hours later I went to turn the Samsung off and latter that night when I went to turn it on it got stuck at the Samsung logo that happen 2 times and on the third time it did not come on & so can't "enter download mode" and the "usb Jig" did not
work. What happen & what do I need to next. Do I take the phone to someone to fix this.
Short version of the story
.Pictures I took 300+ disappeared so when looking for recovery software
.Found a software called "Wondershare Dr.Fone for Android" (the software had "2" Options for recovering. 1 the software would
Auto Root and bring the Samsung back to normal after recovering the pictures or I would have to had the phone already rooted.
. When to the google play store with the Samsung, found a root app download that & "It stated I should download "Kingo SuperUser" to my computer so I did that.
.It failed & got a screen on the Samsung Saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
.Went to Sammobile's site and download Firmware 2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies
.Download Odin3_v3.10.6 had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion
Entered download mode & the Samsung passed
.Everything was back I had it on for 3-4 hours then shutdown the phone later that night went to turn on and it got stuck
at the Samsung logo 2 times and on the 3rd time it would not turn on nor enter "Download Mode"
.Got a "usb Jig" & that did not work and now I am here wondering what do next & what happen to my Samsung Galaxy Note 2 do I need to take to someone to fix it ?
Samsung Galaxy Not 2 Unlocked
SCH-I605V version (Verizon)
my battery was %70 full
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
dseldown said:
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
Click to expand...
Click to collapse
I guess it's the hardware? as It won't come on nor enter Download mode.
Now what, Do I take it somewhere? to fix it what ever it is ?
http://mobiletechvideos.com/
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
SamsungNoteFan said:
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
You cant take it but you can mail it. They unbricked my phone awhile back when something happened. It was good service. I rec'
Click to expand...
Click to collapse