Related
Hello, i am currently trying to root my sisters galaxy s 4g... Her Baseband is T949VUVKI1. Firmware is 2.3.5, Build Number is GINGERBREAD.VUVKI1. i remember flashing her phone to 2.3.5 and download mode working perfectly fine, and for some reason it wont go into download mode at all... the computer is not recognizing her phone either. YES, i do have usb drivers installed otherwise my galaxy s 4g wouldnt be recognized on my computer(odin specifically, not turning yellow). Please help, i have searched everywhere in the internet and tried almost everything... Volume up and down and plug charger, batter out volume up and down usb and battery in etc. PLEASE HELP!! Thank You in Advance.
Nvm
10c
1. Try reinstalling to drivers. Also make sure you're using the same USB port as Windows can be funny about it it sometimes.
2. if download mode is being difficult, go download the Android SDK from www.android.com. Install it, run it, and only download the platform tools. When that's done, open a command promt, CD to where the plaform tools installed (either c:\program files\Android\Android-sdk\platform-tools or c:\program files (x86)\Android\Android-sdk\platform-tools ), then issue the command: adb reboot download.
3. I suggest you check the dev section for bhundven's one-click collection. Uses Java and Heimdall vs. ODIN and works easily.
Sent from my SGH-T959V using XDA App
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Tytan0007 said:
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Click to expand...
Click to collapse
Get it back into download mode, go grab a bhundven's one-click. The one-clicks utilize Heimdall vs. ODIN, which means they use open-source USB drivers instead of the proprietary Samsung drivers. See if that enables the computer to see the phone. If so, flash the one-click
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Tytan0007 said:
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Click to expand...
Click to collapse
That's a good idea. Some people have reported conflicts between the drivers.
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Tytan0007 said:
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Click to expand...
Click to collapse
I wish I had a good answer. ODIN's a funny animal. I've been fortunate and not had any problems with it. I am hoping you are correct - maybe it was just a driver conflict. Let me know how it goes.
didn't work...
You could try downloading a terminal app from the market. Open the terminal and type:
reboot download
See if that does it.
***Update***
Okay, so Oneclick was not working at all no matter what I did with the drivers. However, in all my tinkering with it I installed the Samsung Driver, the Open Source one, and some gadget driver as well from oneclick.
Doing this put all these drivers in my computer. Then I went into my Device manager (Win 7) and looked at my USB driver and I uninstalled everything and went to the stock win 7 usb driver. Then I plugged my phone in and my computer began searching for drivers for this device when it decided that it would be a good idea to load all three drivers at once and voila my phone was then showing up on ODIN 1.85.
I then proceeded to flash my phone with a rom, probably the wrong one considering I was coming from 2.3.5 and my phone boot looped and then soft bricked(sorry if I used these term incorrectly, noobin it).
After, some nervous moment of scouring XDA I found the god-send of a post on getting in to download mode, using odin, and flashing stock 2.3.6 - thank you Raver(I believe). When I did this, my phone magically started obeying ODIN like a devout viking and is now running 2.3.6 superbly.
Keeping with my phones newly found viking heritage, I intend to figure out how to properly root it, update the kernal and modem(not sure which one is best), get CWM, and subsequesntly put in Valhalla Black.
Seeing as though this last rendevous with flashing caused me a little scare I may hold off and wait to see what the next big update is (maybe a port ICS variant) and then go with that.
Anyway, thank you Stephen for helping me out with this and to everyone in this post.
Here's some reading for you Tytan,
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29
PS: Unless you wanna brick your phone, do not flash anything that isn't intended for the SGH-T959V Samsung Galaxy S 4G. You're saying you wanna flash a Vibrant ROM. You can, if you want an expensive paperweight. Happy flashing!
2.3.5 may have been for vibrant...yeah I think I got lucky. I did it prior to knowing about xda.
Sent from my SGH-T959V using XDA App
Tytan0007 said:
didn't work...
Click to expand...
Click to collapse
How are you getting into download mode?
There was a post in another thread where the person apparently was using the power menu to get into download mode or maybe the adb command.
Have you tried both the old fashion volume +/- and plug in usb cable? Or the adb command?
Do you have access to another computer? Believe it or not sometimes just changing computers will make the difference.
Weird when I replied there was no posts other than the ones on the first page...oh well glad its working now.
Hello everybody,
I am new to the forum and also new to Androids. After years of using iPhones and finally becoming fed up Apple, I've decided to try something new (please don't judge my prior smartphone selection and start posting opinions about the 2 operating systems, I do not want this thread to turn into one of the "battle of the phones" thread that I've experienced many times on iPhone forums). My friend recently got an S3 and had no use for his Galaxy S 4g, so he gave it to me so that I could try out an Android. There was one issue though, he said that the phone would not get past the Galaxy S screen and would keep re-booting itself (stuck in a boot loop). He said if I could figure out a way to fix it then it's mine.
That being said, here's my dilemma. I've tried many different methods to get the phone out of a boot loop. The first method I tried was putting the phone into restore mode and selecting the "reinstall packages" option. After this executes I get the message:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After some further research I discovered a nice little program called Odin I read a lot about Odin and how to properly use it. After trying at least 5 different methods to get the phone into download mode with no success, I purchased a jig. The jig did the trick and instantly put me into download mode, I was ecstatic and hopeful that I could now fix the phone with Odin. I connected the phone to my PC in download mode, but Odin still didn't recognize the phone (I tried many versions of Odin, 1.85, 1.87, and the most recent 3.07). I do have the latest drivers for this phone, which I downloaded from Samsung's website. The phone will charge through the computer but the computer does not recognize it otherwise and will not allow me access its mass storage (I am running Windows 7 64 bit). I have tried using a different USB cable, and I have tried to use a different PC, the other PC I used popped up with a message saying that Windows could not successfully download the drivers (that was after I downloaded the drivers from Samsung's webpage and plugged the phone into the computer). I've even tried transferring stock firmware onto an external SD card and loading it onto the phone from restore mode (is that even possible to do?). I have also tried running Odin in compatibility mode, still didn't detect the phone. I should probably also mention that Kies Mini also does not recognize the phone. I asked my friend if he ever tried rooting this phone and he said no, so I'm assuming this issue has nothing to do with a failed attempt to root.
I really want to get this phone working, but I have run out of options to try. I am hoping that someone on here has a solution for me from a similar experience. After reading through the forum, I have noticed that people on here are very helpful and also very friendly; something that I can say is very different from some of iPhone forums I've used. I apologize if there is already a similar thread to mine, I've read through many threads and none of the solutions have worked for me. I also apologize for my first post being so lengthy, I just wanted to state all of the methods that I've tried to fix this phone. Thanks for your replies.
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
itzik2sh said:
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
Click to expand...
Click to collapse
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
It sounds like you can't use Odin because of a windows issue. Try installing linux. I use ubuntu
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
You can also run as live CD or in a virtual machine
Sent from my HTC One X+ using xda app-developers app
hubbs134 said:
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
Click to expand...
Click to collapse
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
I second this... This should fix your driver issues.
Thanks for both of your replies. Odin detected my friends GS3 so I know it's not a Windows issue.
itzik2sh I did what you suggested and now got the command to function properly. I am going to try and finish the tutorial, I will be back soon with results. Thanks.
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Irish Enigma said:
I second this... This should fix your driver issues.
Click to expand...
Click to collapse
I forgot to mention that I can here the sound that a device was just connected to the computer via USB, and a message pops up saying USB device not recognized. When I click on the message it says "One of the USB devices connected to this computer has malfunctioned, and Windows does not recognize it."
Tried a different port? Tried second different port with a different USB cable?
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
Theraze said:
Tried a different port? Tried second different port with a different USB cable?
Click to expand...
Click to collapse
Ok I got the device connected and I got Zadig running, however, there is no option for "Samsung USB Composite Driver" on the drop down list, on "gadget Serial", "Gadget Serial Control (interface 0), and "1.3 HD Webcam (Interface 0)'. What should I do?
On the one-clicks, you don't actually want to use zadig. Apparently it conflicts, which is awesome for something that gets released WITH the tool.
If you're doing manual Heimdall, make sure you've told zadig to list all devices in the menus. Your phone should show up after that.
If you're using a one-click, make sure you're using a USB port on your computer where you have NOT installed zadig, Kies, or Samsung official drivers. Follow the steps in the one-click religiously, and it should cooperate.
Follow the guide %100 then Odin should work
Sent from my HTC One X+ using xda app-developers app
Ok I ended up getting the phone to register in Odin. I flashed it with the stock rom in Odin and it said success. The phone booted and it seemed like it was going to work but then the recovery menu came up. I posted a screen shot of what it says, what action should I take from here? Thanks
I am also in a different boot loop now, before it would load to the first screen (black screen saying samsung galaxy 4g) then restart, now it boots to past the splash screen to where it says "Samsung" and then reboots back to the screen where the pink letters roll across the whole screen. I don't need to flash bootloaders do I?
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
EDIT: Samsung's are easy to brick and hard to debrick it may take a couple of trys
Sent from my HTC One X+ using xda app-developers app
Irish Enigma said:
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
OK GREAT NEWS! After flashing with Odin and that screen popping up, I clicked update from SD card, which failed. I then click system reboot, which brought me into the new boot loop. I put back into download mode and re-flashed with One-Click. Same recovery menu came up as before but when I clicked reboot system it hung at the "Samsung" black screen (after the splash screen) for about 20-30 seconds and then booted up I'm afraid to turn the phone off and see if it reloads lol. Is it safe to say that it is fixed? Or should I still follow your advice and run the proper recovery in Odin and then sideload a new rom? Or take different action? Thanks for all your help guys! Everyone gets a thanks click for being so helpful and friendly on an unhappy/confused/pissed off/ now happy new Android user!
Ok I just put my Tmobile simcard in and the phone is not detecting the sim. Any suggestion?
The IMEI number and baseband both say "unknown", I'm assuming this has to do with the simcard not registering?
hubbs134 said:
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Click to expand...
Click to collapse
What Heimdall package are you applying ?
After JAR package runs you are ready to go.
As I wrote, according to guide you can reinstall "Gadget" driver.
EDIT :
Enigma, if you're not an owner of an SGS 4G please stop advising.
Odin is not the common way since we have MTD ROMs and it had its problems.
hubbs134,
blank IMEI is a serious problem. without a proper IMEI your device is everything but a phone.
Try this : take battery off, press the POWER button for 10 seconds, leave device untouched for 15 minutes and then put battery back and power up.
This could bring your IMEI back to life. If not... maybe another flash will help.
P.S
The 3e recovery image you put on post #14 is a snapshot of the the stock unrooted ROM recovery.
I don't think this has been covered as I have googled till my fingers bled and checked various XDA threads.
I was using the Kingdroid method of updating the bootloader to make it ready for 4.4 TW ROMs as well as Mobile ODIN. I got to the stage of flashing the official 4.4 ROM and I asked for it to boot into ODIN mode so I could do the Bootloader update as well. The only problem is that my laptop seems to not want to recognise my phone as a USB device and I can't take it any further.
I'm sorry if this is in the wrong forum, I couldn't think of anywhere else to put it since I don't know who could help with a solution.
The phone will only go into ODIN mode, hang at the Galaxy Note 3 screen or hang as it tries to reboot into a recovery.
I had made sure all the device drivers/USB drivers were up to date and installed before doing this. I have Windows 8.1 if that matters at all.
Thanks in advance guys,
Paul
PAULO76 said:
I don't think this has been covered as I have googled till my fingers bled and checked various XDA threads.
I was using the Kingdroid method of updating the bootloader to make it ready for 4.4 TW ROMs as well as Mobile ODIN. I got to the stage of flashing the official 4.4 ROM and I asked for it to boot into ODIN mode so I could do the Bootloader update as well. The only problem is that my laptop seems to not want to recognise my phone as a USB device and I can't take it any further.
I'm sorry if this is in the wrong forum, I couldn't think of anywhere else to put it since I don't know who could help with a solution.
The phone will only go into ODIN mode, hang at the Galaxy Note 3 screen or hang as it tries to reboot into a recovery.
I had made sure all the device drivers/USB drivers were up to date and installed before doing this. I have Windows 8.1 if that matters at all.
Thanks in advance guys,
Paul
Click to expand...
Click to collapse
Right click on Odin > Properties and choose Compatibility then run it in Either windows 8 or Windows 7
And uninstall KIES as KIES and Odin don't mix well.
Reboot your lappy and job is done :good:
EDIT: PS - flash total stock 4.4.2 then use a custom ROM as flashing just the BL causes issues.
radicalisto said:
Right click on Odin > Properties and choose Compatibility then run it in Either windows 8 or Windows 7
And uninstall KIES as KIES and Odin don't mix well.
Reboot your lappy and job is done :good:
EDIT: PS - flash total stock 4.4.2 then use a custom ROM as flashing just the BL causes issues.
Click to expand...
Click to collapse
Thanks for the guidance.
Still not working mate. Did everything you said to do, I even put the phone in ODIN then attached it to the laptop and had it attached to the laptop while I put it in ODIN as well. Did those 2 things while launching ODIN too but still no joy.
Meant to say that nothing at all comes up under ID:COM
Any other ideas?
Paul
PAULO76 said:
Thanks for the guidance.
Still not working mate. Did everything you said to do, I even put the phone in ODIN then attached it to the laptop and had it attached to the laptop while I put it in ODIN as well. Did those 2 things while launching ODIN too but still no joy.
Meant to say that nothing at all comes up under ID:COM
Any other ideas?
Paul
Click to expand...
Click to collapse
Try a different Port or even USB cable, USB 3.0 can be iffy sometimes, if that's a no-go try another computer if you can.
EDIT: Try a different version of Odin also if you can, 1.85 is a winner everytime, what version you currently using?
EDIT2: Attached 1.85 for you
radicalisto said:
Try a different Port or even USB cable, USB 3.0 can be iffy sometimes, if that's a no-go try another computer if you can.
EDIT: Try a different version of Odin also if you can, 1.85 is a winner everytime, what version you currently using?
EDIT2: Attached 1.85 for you
Click to expand...
Click to collapse
Cheers fella, I'll give it a crack. My version is Odin3 v3.09. I've looked into the system closer and instead of my device being listed as Samsung it is listed as the Snapdragon 800 processor number and then I have base system device and 8 unknown devices in the same list.
When I right click on the properties it says that the device is not configured correctly, I choose to update the driver and it downloads one only to fail at the install point saying data invalid.
Paul
PAULO76 said:
Cheers fella, I'll give it a crack. My version is Odin3 v3.09. I've looked into the system closer and instead of my device being listed as Samsung it is listed as the Snapdragon 800 processor number and then I have base system device and 8 unknown devices in the same list.
When I right click on the properties it says that the device is not configured correctly, I choose to update the driver and it downloads one only to fail at the install point saying data invalid.
Paul
Click to expand...
Click to collapse
Maybe you need the right usb driver for your phone to be recognized or a adb usb driver perhaps? When the phone is in download mode, windows often list the name differently.
radicalisto said:
Try a different Port or even USB cable, USB 3.0 can be iffy sometimes, if that's a no-go try another computer if you can.
EDIT: Try a different version of Odin also if you can, 1.85 is a winner everytime, what version you currently using?
EDIT2: Attached 1.85 for you
Click to expand...
Click to collapse
Tried a few USB leads and all 3 ports on my laptop but it was a no go. Used v.1.85 as well. The only thing left to do I guess is to try another PC or laptop and keep my fingers crossed.
Paul
hey_joe said:
Maybe you need the right usb driver for your phone to be recognized or a adb usb driver perhaps? When the phone is in download mode, windows often list the name differently.
Click to expand...
Click to collapse
Thanks Joe.
I've tried to install adb but the part that features the drivers fails to install. When I have the Note 3 plugged in I can get to the point that goes to update the drivers but fails to install with a message that the data was invalid.
I had been running 4.4 AOSP on it and my Nexus 7 1G but now it's both that aren't recognised as a USB storage device.
My head is battered now and it looks like the only hope I have of rescuing my phone is if it works on another PC. This is a long shot at this point I think.
Paul
I'm feeling your pain Paul, I'd be devastated if that happened to beautiful note 3. Fingers crossed for you.
Sent from my LG-V500 using xda app-developers app
Definitely try another PC and I think it will work
Sent from my SM-N900 using Tapatalk 2
I have my fingers and toes crossed, gingerdude.
Elhamy, that's my only hope I think. I don't understand what the hell what has happened but I'll have to go the Odin route since that's all I can really get it into. If I run Odin3 on another laptop with the phone plugged in and it isn't recognised, it's getting put through the wall as it's no use to me at that point. I will try to reinstall the drivers through Kies first though, just hope it would still work even though it will be in Odin mode.
Paul
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
kitchenspoon said:
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
Click to expand...
Click to collapse
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
erica_renee said:
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
Click to expand...
Click to collapse
Hi, cheers for the response,
I have tried all of what you have said but unfortunately no PC will see my device, not even an "unrecognized device". I have access to android system reocvery <e3> and Download mode (Odin) but the pc just won't recognized, tried new leads and so forth, nothing.
I went into Odin mode and flashed TWRP in the AP/PDA as all tutorials say (I am skeptical about that, I think this is what caused my phone to brick. BL obviously stands for bootloader, but I wasn't going to question the experts). Afterwards, I went to restart my phone and now I only boot to a broken Odin mode which says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I cannot turn it off without taking the battery out, it reboots immediately. I tried plugging my phone in and running Kies, but I left it to detect devices for 10 minutes and it was still attempting to connect to my SGS2. I have absolutely no idea what to do, I've never gotten this message in Odin before. It was tricky to even get Kies as Samsung took down their link and replaced it with SmartSwitch. Any help would be greatly appreciated.
idk which tutorial youve read but you should of read mine, it uses odin3v1.87 and only pda is ever used and/or needed for the skyrocket.
u could be sol but trying my tut shouldnt hurt.
if theres life theres a chance for it to be revived.
you could try flashing twrp or better yet a full stock firmware so all partitions get reformatted/repartitioned correctly, fingers crossed.
links in my sig
vincom said:
idk which tutorial youve read but you should of read mine, it uses odin3v1.87 and only pda is ever used and/or needed for the skyrocket.
u could be sol but trying my tut shouldnt hurt.
if theres life theres a chance for it to be revived.
you could try flashing twrp or better yet a full stock firmware so all partitions get reformatted/repartitioned correctly, fingers crossed.
links in my sig
Click to expand...
Click to collapse
Thanks; the only problem is that I can't even flash anything at the moment. My phone needs Kies and the drivers first, the Odin/download and recovery modes cannot be accessed otherwise. Kies has never had my phone drivers beforehand as I never had Kies before my phone had problems I should have looked harder for more detailed tutorials like yours first (one of many oversights that I neglected as a newbie). I also forgot to mention I visited the cm wiki to try to flash a newer custom OS and the tutorial asked for Windows users to use Heimdall suite, which failed to work properly in Windows 10 (at least for me). I used it to install a driver which may have replaced my Kies driver but now that I had uninstalled Kies completely and reinstalled it just after my phone broke, I no longer have a way of getting those drivers back since Kies apparently uses the history of my connected phones to install the drivers. I may be completely wrong (I feel I am) so please correct me.
thers a stand alone usb drivers link in the 1stop thread under the utilities section
vincom said:
thers a stand alone usb drivers link in the 1stop thread under the utilities section
Click to expand...
Click to collapse
Well it's not the drivers. Kies simply won't connect for whatever reason. I've tried Kies emergency recovery but it needs my phone to have been plugged in to another computer somewhere in order to get a recovery code or I need Kies to simply detect my phone. I've installed the new drivers multiple times but it doesn't change any results.
fyi you dont need kies for any of my tutorials.
uninstall kies, restart pc and reinstall standalone usb drivers and restart pc.
then follow my guides to the "t"
vincom said:
fyi you dont need kies for any of my tutorials.
uninstall kies, restart pc and reinstall standalone usb drivers and restart pc.
then follow my guides to the "t"
Click to expand...
Click to collapse
I found your stickies and found a link to the proper .tar.md5 file for the stock rom and it works now. Thanks for the help ^^
same prob
Raeffion said:
I found your stickies and found a link to the proper .tar.md5 file for the stock rom and it works now. Thanks for the help ^^
Click to expand...
Click to collapse
i have the same probleme can you sent me the tuto please and links for the correct solution i727 Galaxy S II Skyrocket (SGH-I727)
ayuda
I format the mobile and now when it starts it stays in the twrp crazy and it blinks it stays like an infinite cycle of blinks and when I put it to load with the engine it starts only to the twrp logo it makes. do not abilite the mode
depuration
usb but if I go to the download mode I need your help thanks