Related
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Seifer48 said:
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Click to expand...
Click to collapse
are you putting the phone in download mode before you start the flash process?
EDIT: why did you make a new thread for this here when you already asked the same question in another thread? This isn't development talk please use proper forums next time thanks.
go here...
http://forum.xda-developers.com/showthread.php?t=1311229
that should fix it
Mainly because I didn't want to highjack that thread. Regardless, I felt this was development related hence the post in this forum. Yes, I've put it into download mode (vol up+down+power)
movieaddict said:
go here...
http://forum.xda-developers.com/showthread.php?t=1311229
that should fix it
Click to expand...
Click to collapse
That was actually my first idea. I haven't been able to even attempt this yet though, my issue is that Odin will not progress past "SetupConnection".
It sounds like you don't have all the drivers....
Sent from my GT-I9100 using xda premium
daddymatt said:
It sounds like you don't have all the drivers....
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yea, that was my first thought as well. Would you mind putting yours into Download Mode and checking to see which driver it uses in Device Manager? I'm sure that would be a great help!
Seifer48 said:
Yea, that was my first thought as well. Would you mind putting yours into Download Mode and checking to see which driver it uses in Device Manager? I'm sure that would be a great help!
Click to expand...
Click to collapse
Install Samsung Kies & that will give you all the correct drivers. You can find it by doing a google search.
Sent from my SGH-T989 using XDA App
I actually installed the kies package before I initially tried flashing. I've tried just about every driver package I can think of now.... Random errors are frustrating, especially since its beginning to look like I need a jtag to fix this. I really don't wanna have to build one again.
its not volume up and down plus power. Its pull battery, hold volume up and down, insert usb and then put battery in. a screen will come on the phone that says its dangerous to do this press volume up to confirm. Then make sure phone is recognized by odin and id.com space in odin turns yellow.
At this point I've been pulling the battery, volume up+down+power and plugging in USB. It will be detected by windows, but the device stays at a black screen. I haven't tried pressing volume up after windows detects it though, due to never seeing more than a black screen. Ill go try that and hopefully get somewhere.
Also, Odin has always detected it regardless of what I do.
odin will detect it no matter what but are you using a tmobile version because ive noticed your carrier is att in you sig and youve also posted in the att sg2 forums. if you are trying to use our method to flash an att sg2 guess what my friend you are bricked. It is a different method of rooting.
No luck, when I press volume up nothing happens. Odin detects it regardless.
The particular driver I'm using is "Qualcomm HS-USB QDLoader 9008", I'd love it if someone could plug their device in while in download mode and let me know which driver is in use under device manager. The kies package never installed the download mode driver for me and I had to hunt this one down using a google search for similar issues.
mongo41 said:
odin will detect it no matter what but are you using a tmobile version because ive noticed your carrier is att in you sig and youve also posted in the att sg2 forums. if you are trying to use our method to flash an att sg2 guess what my friend you are bricked. It is a different method of rooting.
Click to expand...
Click to collapse
Lol, yea I know. I have a lot of devices. I am indeed using a TMobile Galaxy S2, SGH-T989. I actually have a phone line with each of the 4 major US carriers. I just use my AT&T line as the primary.
Seifer48 said:
I'd love it if someone could plug their device in while in download mode and let me know which driver is in use under device manager.
Click to expand...
Click to collapse
Not sure if this is what you're looking for, but I see "SAMSUNG Mobile USB CDC Composite Device"
Seifer48 said:
Lol, yea I know. I have a lot of devices. I am indeed using a TMobile Galaxy S2, SGH-T989. I actually have a phone line with each of the 4 major US carriers. I just use my AT&T line as the primary.
Click to expand...
Click to collapse
Does Adb recognize your device?? If so, to make sure you are in download mode run "adb devices" on cmd to see if your device pops up and if it does run "adb reboot download".... This should get you to download mode Then i want you to delete your current .tar file and Re-Download the .tar file!
Ps: both commands run WITHOUT quotation marks
Pss: If odin recognizes your device... Drivers are not the problem
Seifer48 said:
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Click to expand...
Click to collapse
When you make a post like this, you should reference EXACTLY which instructions you are talking about. Referring simply to "the instructions" is pretty useless - which instructions?
Normally, a black screen means you are dead and hardbricked - however the T989 is not a normal device, so what has happened to you is completely unknown. Especially since no one has any clue how you got to where you are.
If Odin is actually recognizing your device, that's good news.
BTW, process is not to insert battery after plugging in USB usually.
It is:
Ensure your device is off (may need a battery pull and reinsert)
Hold VolUP+DN
Insert USB
Entropy512 said:
When you make a post like this, you should reference EXACTLY which instructions you are talking about. Referring simply to "the instructions" is pretty useless - which instructions?
Normally, a black screen means you are dead and hardbricked - however the T989 is not a normal device, so what has happened to you is completely unknown. Especially since no one has any clue how you got to where you are.
If Odin is actually recognizing your device, that's good news.
BTW, process is not to insert battery after plugging in USB usually.
It is:
Ensure your device is off (may need a battery pull and reinsert)
Hold VolUP+DN
Insert USB
Click to expand...
Click to collapse
Sorry, wasn't thinking that well, I was tired lol. Anyways, it was the Root via Odin instructions that Slayher posted. I was mainly posting to see if anyone had encountered anything like that and if so how they fixed it. I've got a black screen that is unresponsive to everything! At this point I'm just gonna say f it and use a jtag. I appreciate everyones help!
Bricked T989 when rootimg with odin
i got the same problem today.
When using ODIN to implement CWM, ODIN stopped
with failure: "could not complete write"
After this i tried to load the stock Rom with odin.
But i get always the same error.
Does anyone have an idea what is going wrong?
Is there a possibility to rebuild the ROM from SDcard?
Thanks for any help
Yes, i'm a total noob, sorry everyone. I tried to root my T Mobile Galaxy S2 using the Kies/Odin method, and now i'm getting nothing but a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I would happily follow those directions, but now Kies won't recognize my device?!?!? I also can not get back into download mode. I have no idea what to do. Is there anyone out there that can help?
Can you still turn your phone on and use it?
Sent from my SGH-T989 using XDA App
He can not use the phone
Sent from my ADR6400L using Tapatalk
Hey I was wondering if u can help my friend out it seems like u were trying to be nice but here's his story he was trying to root his phone I don't know what method but it dud require Odin and some file called Hercules witch I think is cwm but I don't know were he went wrong but now when he tries to boot up it takes him to a black screen that says in red writing Odin mode..product name sgh t898, custom binary: no , current binary Samsung official and below all that there is a phone and yellow warning symbol with it saying firmware upgrade encounter an issue. Please select recovery in kies and try again
Sent from my ADR6400L using Tapatalk
my ADR6400L using Tapatalk
This is what he gets is anyone willing to help
Sent from my ADR6400L using Tapatalk
All you need to do is flash it using Odin. Grab the stock rom from the general forum of the galaxy s2 and flash it using Odin.
Sent from my SGH-T989 using Tapatalk
Did/does Odin recognize the phone? If it does then go ahead and flash the stock Odin firmware package and that should take care of the problem. Same thing happenend to me and all you need to do is set everything up just like normal, go into DL mode and give Odin a few seconds to find a com port and hit start...just pretend the warning is not there.
I have the same thing ...
I was doing a stock upgrade through Kies, and my computer decided to be dumb and install a windows update and restart the computer... I now see the same thing, i had the stock rom, but it was rooted, and when I try to go back in Odin, it never recognizes the phone... Kies won't recognize the phone, neither will Odin... Am I just returning this phone or what?
EDIT: Nevermind, I only bought it 2 days ago, so I just exchanged the phone
Yes, you can flash from that screen -- I managed to brick my Vibrant that way a number of times, and as long as you get that screen (or the Android digging screen) it's recoverable. KIES should be able to recover it as should Odin -- if it DOESN'T work turn OFF the computer (all the way off) and restart it then try again.
Samsung's USB drivers have a habit of getting confused and causing flash failures both in KIES and Odin.
Be aware that if you're trying to use KIES and the "latest" firmware is a non-wipe firmware (as the updates from T-Mobile are) it will happily load onto the phone something that will bootloop into the stock recovery and refuse to start! If you get hosed like this you probably need to Odin back to the ORIGINAL firmware so you get a "full" flash, then use KIES (or ODIN) again to perform the update.
UntamedDeviance said:
I have the same thing ...
I was doing a stock upgrade through Kies, and my computer decided to be dumb and install a windows update and restart the computer... I now see the same thing, i had the stock rom, but it was rooted, and when I try to go back in Odin, it never recognizes the phone... Kies won't recognize the phone, neither will Odin... Am I just returning this phone or what?
EDIT: Nevermind, I only bought it 2 days ago, so I just exchanged the phone
Click to expand...
Click to collapse
Were you able to exchange your device? And if you did, what did the T-Mobile reps ask you? and what did you tell them? I ran into the very same problem. I tried everything but I'm still stuck on that screen. I don't want T-Mobile to think I purposely did something to make the phone that way.
Hope I'm not too late to help: I had same problem and used odin to fix.
Here's what I did:
Download stock kernel in tar form from the Android devel forum. Start odin, click check box in PDA, click PDA button then select the kernel you just downloaded.
Insert usb into your phone (I left my cord connected to my computer). Start phone in download mode (up+down keys). Once it's started ib DL mode, unplug the usb cord, then after just a few moments plug it in again. If necessary, let it set a few moments until Odin recognizes the device (yellow stripe in id:com to the upper left), now click start in odin.
That fixed my problem. After that I read and reread everything I could get my hands on, but I think I tried flashing a i1900 kernel.....big duh to me, but maybe I'm not that dumb after all!! But, soon after I was able to root, and have flashed several custom ROMs since my little bump in the road.
Mrplennium said:
Were you able to exchange your device? And if you did, what did the T-Mobile reps ask you? and what did you tell them? I ran into the very same problem. I tried everything but I'm still stuck on that screen. I don't want T-Mobile to think I purposely did something to make the phone that way.
Click to expand...
Click to collapse
Yeah, I just walked in, brought my receipt and box, and told them I needed a new phone because mine bricked while doing a stock update...they were happy to do it... every one there knew I had previously rooted it as well...
Sent from my SGH-T989 using xda premium
i used this method to root my phone, you need to use odin and flash a new rom
Mrplennium said:
Were you able to exchange your device? And if you did, what did the T-Mobile reps ask you? and what did you tell them? I ran into the very same problem. I tried everything but I'm still stuck on that screen. I don't want T-Mobile to think I purposely did something to make the phone that way.
Click to expand...
Click to collapse
Took mine to a store, they didn't have any white kits in stock so they told me to call and tell them that it doesn't turn on, got a replacement ordered without having to troubleshoot over the phone.
Had that happen the first day I got the device trying to root up. Accdently pulled usb while updating. All i did was Hold VOL UP + DOWN And Plug usb in and download mode came right back up and started the process all over again.
It was a success as.
M&S
Worked!
Thank you!
Overseas and very stressed!!
i had a problem updating -- same error message "firmware upgrade encountered an issue" -- kies can NOT connect to my device. ODIN will not install ICS.. ODIN will not install GINGERBREAD either...
i have the SGH-T989 (t-mobile GS2)
nothing will update. i can't back out to revert to the gingerbread OS i was running previously...
can anyone help me out?
email direct or respond here... thanks for anyone's help
have the same problem
tried to downgrade from ics to 2.3.6 and odin gived me a fail message,after that nothing works i i connect it to the charger it says firmware upgrade encountered an issue.please select recovery mode in kies and try again.
but kies doesn`t recognize me and odin neither.
i can go to download mode with my jig but like i said odin does not give me the yellow symbol.....
is it bricked???
atilla88 said:
have the same problem
tried to downgrade from ics to 2.3.6 and odin gived me a fail message,after that nothing works i i connect it to the charger it says firmware upgrade encountered an issue.please select recovery mode in kies and try again.
but kies doesn`t recognize me and odin neither.
i can go to download mode with my jig but like i said odin does not give me the yellow symbol.....
is it bricked???
Click to expand...
Click to collapse
we don't have ICS... so I'm not sure if you're in the correct section. is your phone's variant the t-mobile t989 hercules s2?
don't do anything with kies, go to download/odin mode and flash a fresh download of whatever you messed up on... or I would just flash a complete stock ROM.. the ones ending with ".tar.md5".. that should save your phone.
Teo032 said:
we don't have ICS... so I'm not sure if you're in the correct section. is your phone's variant the t-mobile t989 hercules s2?
don't do anything with kies, go to download/odin mode and flash a fresh download of whatever you messed up on... or I would just flash a complete stock ROM.. the ones ending with ".tar.md5".. that should save your phone.
Click to expand...
Click to collapse
i used a ics rom from xda and my phone is a european s2 without branding,i just saw this thread here and posted my problem.
like i said odin didn`t recognizes me so i can`t flash anything...
Hey guys,
I was searching the xda pages for a stock odin firmware for my beloved i9000, I didnt find any so I thought that it would be good that i would post the firmware found at sammobile's website and include vodoo odin kernel to get it rooted
I AM NOT RESPONSIBLE FOR THE DAMAGE THAT YOU DO TO YOURE PHONE IF YOU DONT FOLLOW THE INSTRUCKTIONS TO THE TEE!!!!!
And this is for the whole europe!!!!!! Don't know about other parts of the world......
Instructions:
1. Get odin 1.82 or any odin version. Link for odin and the rom are in the next post
2. Unzip the file provided and extract it to somewere where you can find it later.
2. Open up odin with administrator.
3. Switch your phone off and put it into download mode. (the combo is volume down+home+power)
4. Connect your phone to your computer. Odin should reconize your phone and a yellow box will appear.
This is the most important part:
5. In odin, these are the choises you will have to put in:
Pit: s1_odin_20100512.pit
Pda: CODE_I9000XXJVT_CL617736_REV03_user_low_ship.tar.md5
Phone: MODEM_I9000XXJVT_REV_00_CL1064602.tar.md5
Csc: GT-I9000-CSC-HOME-MULTI-OXAJVT.tar.md5
things tickked: repartition, auto reboot, f-reset time. It should tick these automaticly, if it doesent, tick them!!
6. Now click start. It will take a while, so grab something to eat and watch it do its work. When your phone will start the bootanimation and odin says passed, you can disconnect your phone and close odin.
7. Now when your phone has booted up, switch it off and put it back to download mode. (volume down+home+power)
8. Now we will install voodoo kernel. Start up odin with administrator. Connect your phone and in odin there will pop up a yellow box.
9. Put voodoo-kernel-XXJVT-v1.2.tar.md5 in to pda slot in odin.
10. Click start.
11. When your phone is booting up, you can hear a lady talking. This is voodoo. You can disconnect your phone now.
And when your phone has booted up, you have a rooted stock samsung rom.
Links in the next post.
Credits:
totallydubbedhd
madrooster
DOWNLOAD LINK
http://www.mediafire.com/?22vg0suvr7tovqq
size 182.02mb
reserved this
Worked great.... Thank you.
How long will it take on average at the set pit file stage? Thanks,
enya123101 said:
How long will it take on average at the set pit file stage? Thanks,
Click to expand...
Click to collapse
im not actually sure but the whole process takes ~10mins
Sent from my GT-I9000 using Tapatalk 2
Dev section this is . Move ur thread to general plz mate
Sent from my GT-I9000 using Tapatalk 2
Abyv said:
Dev section this is . Move ur thread to general plz mate
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
well the dev area is for roms. this is a rom. so this is in the right area. ppl dont go looking for roms in the general section. so this is in the right area
Sent from my GT-I9000 using Tapatalk 2
Abyv said:
Dev section this is . Move ur thread to general plz mate
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
How can't do that
Please move it. This is not a developed rom.
Sent from my GT-I9000 using xda app-developers app
DanielSanchez said:
Please move it. This is not a developed rom.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
im not able to.
Sent from my GT-I9000 using Tapatalk 2
@up
j3tz3, where is reply?
Adalbert52 said:
@up
j3tz3, where is reply?
Click to expand...
Click to collapse
reply for what?
Sent from my GT-I9000 using Tapatalk 2
Hi,
thanks for your guide, it was easy to follow for me (i hit thanks on the 1st page btw)
got the phone with stock froyo, started to "mod" with your guide to jvt and ended up with jw4 =)
*happy now*
problem
I just followed this thread exactly and the phone doesn't powerup anymore.. what am i to do?
j3tz3 said:
1. Get odin 1.82 or any odin version
Click to expand...
Click to collapse
Hi mate.
Can you please remove the second part of this sentence in your OP?
Odin v1.83 was the last compatible version with the i9000, v1.82 works as good, but majority of the newer versions will freeze or not work at all with the i9000.
Wtf re-partition
j3tz3 said:
Hey guys,
I was searching the xda pages for a stock odin firmware for my beloved i9000, I didnt find any so I thought that it would be good that i would post the firmware found at sammobile's website and include vodoo odin kernel to get it rooted
I AM NOT RESPONSIBLE FOR THE DAMAGE THAT YOU DO TO YOURE PHONE IF YOU DONT FOLLOW THE INSTRUCKTIONS TO THE TEE!!!!!
And this is for the whole europe!!!!!! Don't know about other parts of the world......
Instructions:
1. Get odin 1.82 or any odin version. Link for odin and the rom are in the next post
2. Unzip the file provided and extract it to somewere where you can find it later.
2. Open up odin with administrator.
3. Switch your phone off and put it into download mode. (the combo is volume down+home+power)
4. Connect your phone to your computer. Odin should reconize your phone and a yellow box will appear.
This is the most important part:
5. In odin, these are the choises you will have to put in:
Pit: s1_odin_20100512.pit
Pda: CODE_I9000XXJVT_CL617736_REV03_user_low_ship.tar.md5
Phone: MODEM_I9000XXJVT_REV_00_CL1064602.tar.md5
Csc: GT-I9000-CSC-HOME-MULTI-OXAJVT.tar.md5
things tickked: repartition, auto reboot, f-reset time. It should tick these automaticly, if it doesent, tick them!!
6. Now click start. It will take a while, so grab something to eat and watch it do its work. When your phone will start the bootanimation and odin says passed, you can disconnect your phone and close odin.
7. Now when your phone has booted up, switch it off and put it back to download mode. (volume down+home+power)
8. Now we will install voodoo kernel. Start up odin with administrator. Connect your phone and in odin there will pop up a yellow box.
9. Put voodoo-kernel-XXJVT-v1.2.tar.md5 in to pda slot in odin.
10. Click start.
11. When your phone is booting up, you can hear a lady talking. This is voodoo. You can disconnect your phone now.
And when your phone has booted up, you have a rooted stock samsung rom.
Links in the next post.
Credits:
totallydubbedhd
madrooster
Click to expand...
Click to collapse
RE-PARTITION IS A GREAT WAY TO KILL A PHONE FOR ANY NOOBS/NEWBS i KNOW I DID A YEAR AGO.
Why on earth would you call this a noob friendly tutorial. Every other tutorial I've read since bricking my first try with ODIN where I DID follow the instruction and DID put all the right parts in the right boxes and ODIN failed and I still have that bricked board to this day.
Re-partitioning with ODIN is a bad idea for anyone that does not own a RIFF box to fix the brick or is willing to send their device away to have someone do it for them. It's a mean thing to do if you know what your doing. Noobs maybe noobs and not newbs but getting giggles out of messing their devices up just to show them how smart you are and how dumb they are isn't cool. You yourself wasn't born with all the knowledge and had people thrown stuff like this at you where bricking your device is a very good possibility.
I've been learning this trade (albeit not too much lately making a living has been more important among other things) for about two years now and I have tried re-partitioning 3 times I think on devices I didn't care about due to them not being worth the investment to repair the broken this or that and all 3 have ended up bricks.
Anyway, c'mon don't discourage people from trying to learn this stuff by throwing tricky tutorials that fail most of the time unless the noob or newb manages to get lucky and it works. And just tell people to get lost instead of kicking them in the nuts if you don't want them around.
machv5 said:
Why on earth would you call this a noob friendly tutorial. Every other tutorial I've read since bricking my first try with ODIN where I DID follow the instruction and DID put all the right parts in the right boxes and ODIN failed and I still have that bricked board to this day.
Re-partitioning with ODIN is a bad idea for anyone that does not own a RIFF box to fix the brick or is willing to send their device away to have someone do it for them
Click to expand...
Click to collapse
Flashing the PIT file together with stock firmware (so re-partition checked then) is the best way to unbrick the i9000, very important for unbricking from all custom ROMs higher than 4.3
He has mentioned in the OP the PIT file, so people who read too fast or just briefly carry their own fault by not following the guide.
To check the re-partition without having chosen the PIT file will brick the device, of course.
You can send your phone to the service, they will unbrick it....
@machv5 I've gone back to GB from JB or KK countless times, which requires repartitioning, it's not possible to do without repartitioning, and I've never ended up bricking my phone once.
So if you've managed to brick 3 devices when doing this then you obviously haven't been learning this trade very well now, have you lol
Sent from the immortal Galaxy i9000
When I try to upgrade and initialization through kies it shows up please check the serial number and enter it again,but the serial number is right.
And also when i try to upgrade it while phone is connected ,it downloads the firmware and installation starts but the phone didnt goes to download mode while installing after 100% of installation it comes with an error that it doesn't recognize the phone.
There are some screenshots that i have taken it.
kris4416 said:
When I try to upgrade and initialization through kies it shows up please check the serial number and enter it again,but the serial number is right.
And also when i try to upgrade it while phone is connected ,it downloads the firmware and installation starts but the phone didnt goes to download mode while installing after 100% of installation it comes with an error that it doesn't recognize the phone.
There are some screenshots that i have taken it.
Click to expand...
Click to collapse
can anyone help me in this matter?
I gave up on Kies, biggest pile of **** I have EVER saw in my life. Thanks to the advice of some others I downloaded ODIN for PC and flashed the new firmware rather than using KIES. I will use Google for backing up the phone. One thing you can try is turn on USB Debugging in the Devoloper Options in the Settings menu
Sent from my GT-N7105 using Tapatalk 2
froidy said:
I gave up on Kies, biggest pile of **** I have EVER saw in my life. Thanks to the advice of some others I downloaded ODIN for PC and flashed the new firmware rather than using KIES. I will use Google for backing up the phone. One thing you can try is turn on USB Debugging in the Devoloper Options in the Settings menu
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
is that only solution?is it safe with odin?
kris4416 said:
is that only solution?is it safe with odin?
Click to expand...
Click to collapse
Yeah your pretty safe with ODIN as you are flashing official firmware. Custom ROMS can be a different story make sure you back up your contacts with Google or something just in case, turn USB Debugging on, install Samsung USB drivers and make sure your lead doesn't come unplugged from the computer halfway through the flash there are couple of good guides online, I'll link it for you when I get home from work
Sent from my GT-N7105 using Tapatalk 2
froidy said:
Yeah your pretty safe with ODIN as you are flashing official firmware. Custom ROMS can be a different story make sure you back up your contacts with Google or something just in case, turn USB Debugging on, install Samsung USB drivers and make sure your lead doesn't come unplugged from the computer halfway through the flash there are couple of good guides online, I'll link it for you when I get home from work
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
thanks for the help ! But no any way to fix kies.And in my note s voice handwriting feature is not showing what to do?
kris4416 said:
thanks for the help ! But no any way to fix kies.And in my note s voice handwriting feature is not showing what to do?
Click to expand...
Click to collapse
There may be but I just didn't want to waste any more time on it so I gave up on it! Check this screen shot for your
s note problem. I'm guessing this feature only works with the stock Samsung keyboard as I am using SwiftKey and don't have this option anymore.....unless there is something turned off in sk? Good luck
Sent from my GT-N7105 using Tapatalk 2
EDIT: my bad just realised you meant voice to text...of this I'm not sure as I don't use it, maybe someone else can help with this?
Hi,
I have been a regular visitor of this website and have gained quite a good amount of knowledge through this forum.
I have been with android for the past 2 years and I have loved the android experience.
2 days ago, I read that there was a feature in android whereas the free apps access the internet frequently and use up precious battery power also the paid apps access the google play store in order to verify licenses. Both these kind of apps wakes up itself regularly and this eats up huge amount of battery.
To counter this I was searching for solutions through this website and found that there was an app which could be downloaded and which can handle such kind of scenario. Lucky Patcher. I didn't read the whole thread but I just went ahead and downloaded that app and my phone stopped working minutes after its installation. Upon reading the whole thread I found out that the android phone needs to be rooted in order for that app to work. BIG MISTAKE!
Now my phone is dead. I can start it but it gets stuck on the Samsung Galaxy S3 logo and never goes ahead.
I took the help of this forum to flash a stock ROM of S3 onto my fone using Odin 3.07 and a stock rom downloaded from samsung dash updates dot com.
This is the name of the folder that was downloaded from the website
"Samsung-Updates.com-SGH-T999V_GLW_1_20120818102113_dgbyab64vd"
I tried flashing it using Odin following the procedure but there was nothing happening on the software or on the phone. I kept the phone attached while Odin was "Initialising" for around 4-5 hours. I slept along that time, and when I woke up, it was still there. I was supposed to get "PASS!" on Odin but I didn't get that. I downloaded the previous versions of the stock ROM and tried that but all in vain.
Phone model: SGH-T999V (Wind Mobile, Canada)
Now I can't find a solution to this problem and this is my last resort. By the weekend I will go to one of those mobile stores which I haven't seen in ages, but will have to go there as I am unable to revive back my fone. And I utterly miss using it.
If there is anything any of you guys can help me with, I will be more than happy to reply to any further information you need.
Thank you all for reading, and thanks a million for even thinking of helping me.
God Bless you all.
-shanxthechashmish
I can't get in recovery mode (Home+volumeUP+Power). it vibrates once but the screen remains blank.
I can get into downloading mode (Home+volumeDown+Power). which gives me two options, one to continue and the other to cancel.
(May be this helps to determine whether my phone has been bricked or not!)
Using ODIN, the following information is given and is stuck at this only...
"<OSM> KIES_HOME_T999VVLDLL1_T999VYVLDLL1_CL616748_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation.."
Usually, if you're stuck.during boot you just need to factory reset. Are you sure you're trying the right way to boot recovery? Hold volume up, home and power, when it vibrates, release power but continue holding volume up and home. Some blue text should flash at the top of the screen (you can let go of all buttons now) and it should boot recovery.
No idea why Odin isn't working. Do you have kies installed? If so, get rid of it, reboot and try again.
You could try flashing CWM or TWRP (see my Sig). Then boot recovery and factory reset or flash a Rom.
Sent from my SGH-T999L using Tapatalk 4
Sounds like the drivers are missing. Or you need to run ODIN as administrator
I'm with @KAsp3rd, the computer is not seeing the phone, reinstall the USB drivers try again.
Here is a guide I made:
1. Download and install USB Drivers from here: Thanks to @DocHoliday77 for hosting
http://www.androidfilehost.com/?a=show&w=files&flid=1368
2. Download and extract ODIN 3.07 from here: Thanks to @DocHoliday77 for hosting
http://www.androidfilehost.com/?a=show&w=files&flid=1369
3. Download Stock ROM image (.tar file) from here: Thanks to @DocHoliday77 for hosting
http://forum.xda-developers.com/showthread.php?t=1949687
4. Save all open files and reboot computer
5. Boot phone into Download mode (also called ODIN mode) by shutting down the phone and holding Volume Down & Home then pressing Power until it vibrates, still holding Volume Down & Home buttons, until the "Yellow Triangle" screen shows up.
6. Plug phone into computer and open ODIN 3.07 and make sure that only "Auto Reboot" and "F. Reset Time" are checked.
7. Click on the "PDA" button (right side about half-way down), browse for ROM .tar file, click "Open" button.
8. Click "Start" button and watch to "Reset" or "Fail" to show in the 1st square (upper left side),
9. Phone will reboot
10. Leave phone alone for 10mins+ to let all of the first time boot stuff complete.
Good luck with it.
DocHoliday77 said:
Usually, if you're stuck.during boot you just need to factory reset. Are you sure you're trying the right way to boot recovery? Hold volume up, home and power, when it vibrates, release power but continue holding volume up and home. Some blue text should flash at the top of the screen (you can let go of all buttons now) and it should boot recovery.
No idea why Odin isn't working. Do you have kies installed? If so, get rid of it, reboot and try again.
You could try flashing CWM or TWRP (see my Sig). Then boot recovery and factory reset or flash a Rom.
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
yes, I was doing the right way with the boot recovery. There was a blue text when the SAMSUNG logo flashed, but nothing after that. I let go off the power button while holding the power up and home buttons, but nothing went ahead.
I dont have kies installed. My laptop has a fresh win 7 ultimate installation. I got the usb drivers for samung already installed, it detects the phone everytime on one of the COM ports.
I'll go through the flashing CWM and TWRP. you meant your signature, right?
sorry for being such a newbie..
KAsp3rd said:
Sounds like the drivers are missing. Or you need to run ODIN as administrator
Click to expand...
Click to collapse
TI reinstalled the drivers using the Samsung flashing kit that was available here on xda developers.
I am not sure if ODIN is run as admin. I guess I need to try that one tonight. In class right now, too anxious to study..
wil post up the results as soon as i reach back home..
shanxthechashmich said:
yes, I was doing the right way with the boot recovery. There was a blue text when the SAMSUNG logo flashed, but nothing after that. I let go off the power button while holding the power up and home buttons, but nothing went ahead.
I dont have kies installed. My laptop has a fresh win 7 ultimate installation. I got the usb drivers for samung already installed, it detects the phone everytime on one of the COM ports.
I'll go through the flashing CWM and TWRP. you meant your signature, right?
sorry for being such a newbie..
Click to expand...
Click to collapse
Yes, in my signature. But the others may still be correct. When you connect and open Odin does it show the port number in the top left area? If not then it's probably a driver issue, even if they're installed. Happens a lot believe it or not. Also try other usb ports on the computer.
If you can flash recovery in Odin though, this is all irrelevant of course! Either way let us know what happens.
Sent from my SGH-T999L using Tapatalk 4
DJ_SpaRky said:
I'm with @KAsp3rd, the computer is not seeing the phone, reinstall the USB drivers try again.
Here is a guide I made:
1. Download and install USB Drivers from here: Thanks to @DocHoliday77 for hosting
http://www.androidfilehost.com/?a=show&w=files&flid=1368
2. Download and extract ODIN 3.07 from here: Thanks to @DocHoliday77 for hosting
http://www.androidfilehost.com/?a=show&w=files&flid=1369
3. Download Stock ROM image (.tar file) from here: Thanks to @DocHoliday77 for hosting
http://forum.xda-developers.com/showthread.php?t=1949687
4. Save all open files and reboot computer
5. Boot phone into Download mode (also called ODIN mode) by shutting down the phone and holding Volume Down & Home then pressing Power until it vibrates, still holding Volume Down & Home buttons, until the "Yellow Triangle" screen shows up.
6. Plug phone into computer and open ODIN 3.07 and make sure that only "Auto Reboot" and "F. Reset Time" are checked.
7. Click on the "PDA" button (right side about half-way down), browse for ROM .tar file, click "Open" button.
8. Click "Start" button and watch to "Reset" or "Fail" to show in the 1st square (upper left side),
9. Phone will reboot
10. Leave phone alone for 10mins+ to let all of the first time boot stuff complete.
Good luck with it.
Click to expand...
Click to collapse
Thnaks for this detailed list.
but i know this drill, the only problem being that the phone is not going anywhere after the step where the ODIN has already flashed the file on the phone.
It gets stuck while "Initializing.." I have posted that as an update on my Post.
As KAsp3rd said that I must try running it as an administrator, I might do it tonight and will let you all know what it gave me..
Thanks for all the help..
I think we posted at the same time so did you see my post? Do you remember if Odin had the port number at the top left? In the Odin output it said ID:0, so it may not be seeing the phone.
Sent from my SGH-T999L using Tapatalk 4
@DocHoliday77
Yes, it shows the COM port on the top left corner of the ODIN.
I have also uninstalled and reinstalled the driveres several times, but with no effect.. I am thinking the run as administrator is the one thing I havent thought of or tried or seen anywhere on the forum.
I will post the result of that as well by tonight.
And thanks for hosting so many files online. I downloaded the one that was needed for the Stock Firmware.
Ok, and in case you don't know, uninstalling the driver software isn't enough on its own. Go into device manager, right click and either update drivers, or uninstall, then install the new driver package.
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Ok, and in case you don't know, uninstalling the driver software isn't enough on its own. Go into device manager, right click and either update drivers, or uninstall, then reboot computer, then install the new driver package.
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
Windows, always reboot after uninstalling any drivers.
@DocHoliday77
I tried that thing again. Reinstalled the drivers after uninstalling and rebooting. there is still no response.
I gave it to one of my friends, he tried putting in the recovery file and now the screen says "Installation of the software has been interrupted, please restart to begin"
I'll post the screenshot in the morning now.
Also, @KAsp3rd : I tried running Odin as administrator, but the same thing happened. It used to get stuck at "Initialization"
Any more advices ?
shanxthechashmich said:
@DocHoliday77
I tried that thing again. Reinstalled the drivers after uninstalling and rebooting. there is still no response.
I gave it to one of my friends, he tried putting in the recovery file and now the screen says "Installation of the software has been interrupted, please restart to begin"
I'll post the screenshot in the morning now.
Also, @KAsp3rd : I tried running Odin as administrator, but the same thing happened. It used to get stuck at "Initialization"
Any more advices ?
Click to expand...
Click to collapse
Is it the phone that says installation interrupted? When he tried flashing the recovery did he use odin? Did it seem to flash properly?
Something else I don't thonk hss been mentioned is to try a different usb cable. Preferably one thst came with the phone, or another device. (Some cables sold for recharging are not capable of data transfer on these devices).
Also, try all ports on the computer, and unplug all unnecessary peripherals.
If something happened and you got a bad flash, it could be bricked. Can't remember if you tried KAsp3rd's unbrick method already.
Another thing you can try to get recovery installed is to adb shell into the device and using the dd command, dump recovery to the phone. Youll have to have the android sdk installed to do this though.
Its hard to say what's really needed at this point though. Usually if you can get download mode, you can Odin the stock firmware. Most Odin problems are due to driver and cable issues. (Is Windows fully updated?)
Even though you can get download mode, the debrick method may still help, but I'm just not sure. Maybe I'm missing something.....
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Is it the phone that says installation interrupted? When he tried flashing the recovery did he use odin? Did it seem to flash properly?
Something else I don't thonk hss been mentioned is to try a different usb cable. Preferably one thst came with the phone, or another device. (Some cables sold for recharging are not capable of data transfer on these devices).
Also, try all ports on the computer, and unplug all unnecessary peripherals.
If something happened and you got a bad flash, it could be bricked. Can't remember if you tried KAsp3rd's unbrick method already.
Another thing you can try to get recovery installed is to adb shell into the device and using the dd command, dump recovery to the phone. Youll have to have the android sdk installed to do this though.
Its hard to say what's really needed at this point though. Usually if you can get download mode, you can Odin the stock firmware. Most Odin problems are due to driver and cable issues. (Is Windows fully updated?)
Even though you can get download mode, the debrick method may still help, but I'm just not sure. Maybe I'm missing something.....
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
I have the original cable with me, the one that came with the s3.
he tried using ODIN, but thats as far as I know. He said something about using Kies to flash the rom as well. not sure what.
No, I didn't try KAsp3rd's unbrick method. Could you please guide me where could I find that?
Also, everything you said after this unbrick method simply doesn't make any sense to me. May be some guided instructions would be helpful.
And yes, the windows is fully updated, no issue on that.
Where can I find the unbrick method?
If you want to just search for android sdk. It'll find Google's page for it and instructions. Should also find some good guides on installing and using. All I'd 've doing is searching for then repeating it back to you, so it'll be easier for both of us if you just go to the source. I think it's developer.Google com or something similar.
And she'll basically connects to your phone and allows you to run commands as if you were using the terminal emulator.
The debrick thread is stickies in development.
Sent from my SGH-T999V using Tapatalk 4
what is the official stock firmware can i download directly? and what are name of the firmware and how long the procedure to flash that?
Firmware thread stickies in development section. Link is also in my Sig. Everything you need to know and download to get started is in that thread.
Sent from my SPH-L710 using Tapatalk