I'm pretty good with computers even though I don't really code (I do pretty much everything but that) yet I've had nothing but trouble trying to flash CWM 6.0.1.9 to a GT-I9300 version of SGS3.
Here's a brief list of the various approaches I've tried, as a result of my own intuition and following the advice given to people in similar situations across this forum and dozens of others. I might not have achieved my goal yet, but I assure you I'm persistent and thorough!
I've tried four different PCs at this point, three running Windows 7 (one desktop, one laptop, one nettop - all 32-bit) and one running Windows XP.
I've tried installing Kies, then removing Kies and just installing standalone "SAMSUNG_USB_Driver_for_Mobile_Phones".
I've tried various USB ports on all the systems
I've tried various ways of plugging in the phone (you know, before/after it's in download mode), making sure there are no other devices in the USB ports, restarting before loading Odin, making sure Odin is run as Administrator, making sure Odin is running before/after the phone is plugged in, keeping the phone plugged in via USB with the battery out then putting the battery in and booting to download mode etc etc.
I've tried about five different versions of Odin at this point. The phone appears in all of them - sometimes the COM port is yellow, sometimes it's blue. Bit confusing but I've given to understand the colour differs depending on the Odin version.
Suffices to say I've been as thorough as I can think to be. But in all cases, the "GT-I9300_ClockworkMod-Recovery-Touch-6.0.1.9.tar" cannot be flashed to the phone... it just appears to start and then stalls, eventually failing when it's left long enough, with the word RECOVERY in a white box at the top of Odin but the file never getting sent to the phone, it seems. I have similar problems trying all the various different things when trying to flash an older version of CWM to a Galaxy Ace, except this time it gets stuck at the SetupConnection part and eventually fails. It's very frustrating!
Honestly I don't know what else I can try. I'm really hoping for as many suggestions as possible, because unless I can get CWM installed on the S III there's no way I can back up the stock version of Jellybean via Nandroid, install Cyanogenmod 10.1 and finally enjoy the benefits of a fully rooted phone.
Thanks in advance to anyone who throws out an idea that makes me look at this in a different way and helps me solve the problem.
Have you got Kies installed? If so make sure it is disabled I'm systray, also run Odin as administrator
slaphead20 said:
Have you got Kies installed? If so make sure it is disabled I'm systray
Click to expand...
Click to collapse
I did have Kies installed, but then ditched it on all four PCs and just used the standalone drivers as mentioned, so I'm not having to worry about disabling Kies from systray or killing it completely via Task Manager,
As I understand it from reading lots of other threads across various forums, the drivers are all you really need Kies for. Unless there's something else it does I'm not aware of... as I say I'm trying every option I can think of, every combination of possibilities to get this thing done.
slaphead20 said:
also run Odin as administrator
Click to expand...
Click to collapse
As I say, whether I run Odin as Admin or not doesn't appear to make a difference, sadly. I will say that all four Windows PCs I mentioned are logged on as the master Admin account and I have all the "nag screens" of Windows disable ("Open File - Security Warning" for example) too.
Thanks for the reply.
Try it with a newer version of ClockwordMod Recovery. That may help.
m0cha5hake said:
Try it with a newer version of ClockwordMod Recovery. That may help.
Click to expand...
Click to collapse
I'm tempted to try this when I get the chance, but the thing is when I open the TAR file under the PDA column in Odin and try to flash the S III it correctly identifies the "recovery.img" file inside, it just never seems to send it to the phone even though USB Debugging is enabled before booting into download mode. I'd guess another version (older or newer) would have the same problem?
Using Samsung USB cable ???
jje
JJEgan said:
Using Samsung USB cable ???
jje
Click to expand...
Click to collapse
Yep, official Samsung USB cables that came with the phones (Galax yS III/Galaxy Ace).
I wouldn't want to state the obvious, but have you tried flashing a different file?
The fault could be with the file, not with Odin/Windows/Phone
And as far as Kies goes, I know from experience that if you uninstall it, it still leaves bits of itself around so still worth checking in Task Manager that there are no parts still running in the background. As we know, Odin and Kies don't get along.
Something that springs to mind - what version of Android are you using? 4.0.x, 4.1.x, pre 4.x?
Still no joy trying to flash the S III via Odin on Windows. To be honest it's far too much trouble for what should be a simple recovery flash so I think I'd like to do it under Ubuntu instead, I can make a Live USB stick and boot from that then install any needed files (I'm guessing Heimdall via Terminal could do it). Any tips on the easiest way to install CWM on the S III when running Ubuntu? I watched this video and I'm wondering how accurate it is...
Ubuntoo no idea very little posted suggested a Google search might bring up a how to even if for a different model .
It reads like a critical step is missing in your attempts to root via windows for some reason .
It is a 5 min job for most users .
jje
JJEgan said:
It reads like a critical step is missing in your attempts to root via windows for some reason
It is a 5 min job for most users
Click to expand...
Click to collapse
I know, and I've been thorough, that's why I'm so confused I can't seem to do something relatively easy. Odin just hangs and never sends the recovery.img from the TAR file to the phone... it looks like it goes to start with the RECOVERY box above the S III's ID:COM port and then never flashes. It's so odd.
Are you rooted?
slaphead20 said:
Are you rooted?
Click to expand...
Click to collapse
No that's the thing - I don't want to root until I can do a full backup of the original Jelly Bean with CWM - getting CWM on there is basically the first hurdle. But at this point I suppose it might be a good idea to compromise, just to get it done. Not sure really. Don't have enough experience rooting phones to know for sure.
Not sure but I think you need root access to install CWM recovery
m0cha5hake said:
Not sure but I think you need root access to install CWM recovery
Click to expand...
Click to collapse
With the S III you might be right, however I couldn't install CWM for the Galaxy Ace using different Odin versions like 3.04 and 3.07 either, and that phone is already rooted with CM 7.2 and already has an older version of CWM on it. Which leads me to believe that something is amiss with Odin and Windows, seeing as I've tried it on four different Windows machines (3 WIndows 7, 1 Windows XP). It's baffling and frustrating.
If the Ace is already rooted just flash a newer version of CWM in recovery
m0cha5hake said:
If the Ace is already rooted just flash a newer version of CWM in recovery
Click to expand...
Click to collapse
I did. I was just making the point that even on an already rooted/CWM enabled phone a new version of CWM was not able to be flashed across via Odin.
m0cha5hake said:
Not sure but I think you need root access to install CWM recovery
Click to expand...
Click to collapse
Yes you need to be rooted to install cmw
Use chainfire recovery to root and install cwm recovery mate
Then you can flash touch version
Sent from my GT-I9300 using Tapatalk 2
chubby65 said:
Yes you need to be rooted to install cmw
Use chainfire recovery to root and install cwm recovery mate
Then you can flash touch version
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I was under the impression that newer versions of Clockworkmod don't need Chainfire first, is that wrong?
I want to thank everyone who has chipped in so far - I'm learning a lot!
zekepliskin said:
I was under the impression that newer versions of Clockworkmod don't need Chainfire first, is that wrong?
I want to thank everyone who has chipped in so far - I'm learning a lot!
Click to expand...
Click to collapse
Not sure mate I've always used chainfire to root and install cwm recovery works every time for me
Tried the touch version but always reverted back due to too many problems
Sent from my GT-I9300 using Tapatalk 2
Related
So I rooted my Note a few weeks back using the non-counter advancing rooting method via odin. Worked flawlessly, and I'm rooted without issue. Tired of waiting for stock ICS to come out so I want to start flashing ROM's. Trying to install the newest CWM through Odin....well Odin doesn't recognize when the phone is connected. Tried 2 different windows 7 VM's and one W7 machine. I flashed via one of the VM's and it worked fine. It's not working on any machine that I have. I also have a mac book pro, but no idea if there is a apple Odin. What do I do? Don't have the android APK and really don't wanna go that route through ADB.
Can I just reboot into recovery and 'install via sd' or whatever the selection is, navigate to CWM touch recovery zip and install? or will that potentially do some serious damage?
Also if it's available on the CWM website as a DL why isn't it an option through the app to install? Would make my life WORLDS easier at this point.
A rooted phone would not interfere with Odin, completely unrelated. Perhaps your cable is bad, or you are installing the wrong drivers.
That said, once you have CWM on your phone, there should be no reason to use odin again. The updates for CWM are flashable via CWM. Most every single ROM is flashable via CWM. I can't really tell from your description if you were successful installing a custom recovery yet.
jpeg42 said:
A rooted phone would not interfere with Odin, completely unrelated. Perhaps your cable is bad, or you are installing the wrong drivers.
That said, once you have CWM on your phone, there should be no reason to use odin again. The updates for CWM are flashable via CWM. Most every single ROM is flashable via CWM. I can't really tell from your description if you were successful installing a custom recovery yet.
Click to expand...
Click to collapse
Trying to install a custom recovery. Sorry may not have made that clear in my rant. I've tried a couple different cables, and same luck. I DLed the CWM app from the Google Play, but have not installed a custom recovery. Trying to get CWM touch installed. Galaxy Note isn't an option when I try and install a custom recovery(CWM Touch Recovery...or hell any CWM recovery Note isn't an avialable model) via CWM.
So the options I've found so far are: Install custom recovery(CWM) via Odin, or install via ADB using android APK.
Are there other options to installing CWM recovery?
Sorry kind of a newb to all of this. I had a Dell Streak before this as my first android and it was a PITA to install Custom ROM's and root that I didn't mess with it much. Did root it and managed to soft brick my phone and bring her back to life. lol Then figured it was too much a pain to deal with.
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
froidroid said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
This...if not restart everything from scratch. Uninstall the drivers and re-install them again and restart Odin. Also make sure you are using the latest version of Odin.
froidroid said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
Correct isn't recognized in DL mode. The phone is recognized just fine when I plug it in regularly. Can transfer back and forth all day long.
The ICS ROM I wanna try uses CWM recovery to install. So trying to get everything to line up as to not end up with a brick. lol
babymatteo said:
This...if not restart everything from scratch. Uninstall the drivers and re-install them again and restart Odin. Also make sure you are using the latest version of Odin.
Click to expand...
Click to collapse
Believe I've done that before, but will try again. Latest version of Odin higher than 1.8.5 or something like that? If so that's what I'm using.
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
darkion2411 said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
Not sure what's going on with XDA, but my reply didn't post. So here goes: Yes that is correct I would boot into DL mode and odin didn't see my phone.
So I opened one of my VM's( the one previously used to root) uninstalled/reinstalled the drivers and voila odin sees my phone again. CWM touch recovery installed. Now off to flash Team Perfections ICS. Only chose them as they have a step by step video of installation and it seems stupid easy. Also seems to be the most stable from reading. Could be wrong. I'll try it out and wait for official CM9.
Have you tried using a different PC. I remeber my desktop wouldnt let me odin all the sudden one day. I tried my laptop worked no problem. using a VM sounds sketchy id be afraid there were too many facets or some risk of data corruption on its way. That may be incorrect but data > virtual hardware > hardware > phone. just too much for me -_-
Wing_Zero_Custom said:
Have you tried using a different PC. I remeber my desktop wouldnt let me odin all the sudden one day. I tried my laptop worked no problem. using a VM sounds sketchy id be afraid there were too many facets or some risk of data corruption on its way. That may be incorrect but data > virtual hardware > hardware > phone. just too much for me -_-
Click to expand...
Click to collapse
I tried my physical windows machine and it wouldn't even install the drivers. Failed every time regardless what I did.
I got the VM to work fine. CWM recovery touch is installed now.
sukemecuke said:
Not sure what's going on with XDA, but my reply didn't post. So here goes: Yes that is correct I would boot into DL mode and odin didn't see my phone.
So I opened one of my VM's( the one previously used to root) uninstalled/reinstalled the drivers and voila odin sees my phone again. CWM touch recovery installed. Now off to flash Team Perfections ICS. Only chose them as they have a step by step video of installation and it seems stupid easy. Also seems to be the most stable from reading. Could be wrong. I'll try it out and wait for official CM9.
Click to expand...
Click to collapse
All roms are that easy to flash once you have cwm, it's just booting into recovery, wiping, and flashing.
Try em all and see which one works best fir you
studacris said:
All roms are that easy to flash once you have cwm, it's just booting into recovery, wiping, and flashing.
Try em all and see which one works best fir you
Click to expand...
Click to collapse
I hear ya. Just when I start reading about some ROM's they say: oh and you need to flash this, this and this or else your phone will blow up and likely kill your whole family.
Being somewhat new to the flashing business just flashing ONE zip file is enough for me. Yet alone a bunch of other things. Just starts to confuse me with the multiple flashes......do I install all the same( as far as "flashing" goes)? Just boot into recovery navigate to file...double click and it'll do it's thing? If so I suppose that's not all that difficult. I like the one and done approach though. lol
Yup.
If there are multiple zips, flash them all like the main ROM.
Sweet! Flashed the Objection ICS. Like it so far. Seems like the modem is kinda all over the map for lte speeds.
Sent from my SAMSUNG-SGH-I717 using XDA
Hello Sirs,
Today I was about to flash the long awaited CM9-RC1 on my Samsung Galaxy S2 device with ROM Manager. After downloading it with Rom Manager I checked the three options:
Wipe Factory/Reset
Wipe Dalvik
Backup Device
Phone reboots and screen turns black. I waited for a good 15 minutes yet nothing happens. I popped the battery out and tried to fire it up again but now it wont start properly. It will be detected by computer as a "Unrecognized Device" only. The phone shows the Samsung logo + the flashcounter warning I assume? (Yellow triangle with exclamation mark.).
I cant access recovery-mode (clockworkmod) the only thing I am able to access is "Downloading Mode" but the device remains "Unrecognized Device" by computer. I did a little research about this problem - I only found some tips on changing cables/clean usb-port. None of which worked out to any advantage. I cant access the phone with adb either, and USB Debugging is not enabled as far as I know.
Odin nor Heimdall wont recognize the phone.
Downloading Mode
Code:
ODIN MODE
PRODUCT NAME: GT-i9100
CUSTOM BINARY DOWNLOAD: YES (2 Counts)
CURRENT BINARY: CUSTOM
Previously installed on the phone was 20120624-CM9-NIGHTLY along with Siyah Kernel SGS2 v3.3.2.
Worth to mention is that this happened to two phones at the same time. My brother also flashed his today and got the same result. Also with Siyah kernel as mentioned above.
I've tried 4 different USB-cables, and two different Windows 7 computer. Also I've reinstalled one of the computers to try a little more. No success.
This tells me that there is something with the Siyah kernel that borks the phone somehow. Yet it seems possible to fix it since I can access the "Downloading Mode". Dont you think? Anyone with similiar issues and maybe have a solution for this?
And if there is no software solution to this is it possible that a USB-JIG would sort this out?
Sincerely,
Your problem is likely rom manager instead of siyah kernel or otherwise. Rom Manager does not work properly on our phone and is known to cause problems when installing things with it. Did you install drivers with the other computers you tried?
Went through this today too. My fault for using Siyah
Don't freak out, just grab Odin 1.85, and flash the noob-proof build available in the Discussion thread from Download Mode.
Your data will be wiped btw. A safer way would be to flash the Recovery via Odin, and once in recovery, reflash CM9.
The lesson of the story is to not use Siyah, as it's not supported under CM9
Nushio said:
The lesson of the story is to not use Siyah, as it's not supported under CM9
Click to expand...
Click to collapse
That's not true. There's a whole thread full of people using Siyah and CM9 here.
Nushio said:
Went through this today too. My fault for using Siyah
Don't freak out, just grab Odin 1.85, and flash the noob-proof build available in the Discussion thread from Download Mode.
Your data will be wiped btw. A safer way would be to flash the Recovery via Odin, and once in recovery, reflash CM9.
The lesson of the story is to not use Siyah, as it's not supported under CM9
Click to expand...
Click to collapse
Well I am kinda freaking out since the device keeps showing up as "Unrecognized Device"! So I am not able to flash anything since it doesnt show up anywhere. I cant do anything to touch the phones software. Its just b0rked I guess.
I actually have the same problem with a S2 LTE which suffered from the same symptoms as stated above. Im starting to suspect maybe a crappy USB cable is the underlying reason for this, causing the usbport on the phone to fry or something.
Did you install drivers with the other computers you tried? Yes sir I installed the proper drivers there aswell.
I tried flashing the latest RC of cm9 and it went well even though i have siyah as the kernel. You shouldn't have flashed through rom manager. I flashed it through recovery
Sent from my GT-I9100 using xda premium
ephraim033 said:
I tried flashing the latest RC of cm9 and it went well even though i have siyah as the kernel. You shouldn't have flashed through rom manager. I flashed it through recovery
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I hate ROM Manager. Is some app that I will never trust. The only purpose of ROM Manager: money, and placebo [you think it's the easiest way to flash stuff]. Can't find out why they put this in the ROM. At least they could make some OTA download. What is the Software update for at settings? Don't know...
ROM manager is crap. Never use it. That is what caused the issue. I am using CM9 based ROM with Siyah without any problem.
marcellocord said:
I hate ROM Manager. Is some app that I will never trust. The only purpose of ROM Manager: money, and placebo [you think it's the easiest way to flash stuff]. Can't find out why they put this in the ROM. At least they could make some OTA download. What is the Software update for at settings? Don't know...
Click to expand...
Click to collapse
ambar_hitman said:
ROM manager is crap. Never use it. That is what caused the issue. I am using CM9 based ROM with Siyah without any problem.
Click to expand...
Click to collapse
So what are you suggesting I should use instead? I'm hoping to return
the phone in topic when ive jigged it and demand a new one since there is still warranty hehe.
Don't use Rom Manager with kernels which have CWM/CWRecovery I.E. Siyah, CWM is more than capable of doing all the flashing/backups/restores/etc you need. If you end up using CM9 & Siyah again, make sure you freeze Rom Manager with TI or similar.
goopen said:
So what are you suggesting I should use instead ?
Click to expand...
Click to collapse
MistahBungle said:
Don't use Rom Manager with kernels which have CWM/CWRecovery I.E. Siyah, CWM is more than capable of doing all the flashing/backups/restores/etc you need. If you end up using CM9 & Siyah again, make sure you freeze Rom Manager with TI or similar.
Click to expand...
Click to collapse
So the weirdest of things just happened. I left the phone discharging with the download mode active during the night. Today I bought a new phone (4100SEK /$585USD) and I thought maybe, just maybe it works now. I put the device in Download Mode and now popped it into the computer with the same cable as yesterday. And there it was "Device installed successfully!". Holy ****. Fired up Odin v1.85 and just pushed that damn recovery image onto the phone and bam! Rebooting, works like a charm. Now thats just f**king unbeliveable. But of course this wouldnt have happened if I DIDNT buy a totally new phone. The irony.
Moderator you may close this thread and save it for future reading.
Sincerely,
Another satisfied customer
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
I'm trying to buy a cheap smartphone for my girlfriend. Just bought a used Vibrant from eBay only to find it had an IMEI blacklisted by T-Mobile. Already had put CM 10.1 on it and she loved it so I'm pissed.
Any tips for buying a decent used smartphone for under $100? Vibrant seems like one of the best and I'm partial to Samsung. Any recommendations for the fastest Android 4.x ROM with the best battery life for the Vibrant?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm having a really hard time reflashing to stock. All the write-ups seem to be out of date. I tried the AIO Vibrant Toolbox 2.5 and can't get the phone to show up in Odin. Then I tried these instructions:
http://forum.xda-developers.com/showthread.php?p=18765728
What's the best version of Odin to use currently? Is there a simpler, reliable way to flash back to stock from CM?
VQ30DE said:
I'm having a really hard time reflashing to stock. All the write-ups seem to be out of date. I tried the AIO Vibrant Toolbox 2.5 and can't get the phone to show up in Odin. Then I tried these instructions:
http://forum.xda-developers.com/showthread.php?p=18765728
What's the best version of Odin to use currently? Is there a simpler, reliable way to flash back to stock from CM?
Click to expand...
Click to collapse
Are you putting the phone into download mode before connecting to Odin? You must be in download mode, I prefer Odin 1.7, every other version hangs on me for some reason. I always follow the guide below, never messed with AIO toolbox. Follow this guide to get back to stock JFD (2.1) http://forum.xda-developers.com/showthread.php?t=849028
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Are you putting the phone into download mode before connecting to Odin? You must be in download mode, I prefer Odin 1.7, every other version hangs on me for some reason. I always follow the guide below, never messed with AIO toolbox. Follow this guide to get back to stock JFD (2.1) http://forum.xda-developers.com/showthread.php?t=849028
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, had the phone in download mode and was using Odin 1.7. I have the latest Samsung drivers for WIndows installed, and when I mount the SD card the phone shows up properly. That guide you linked to was one I tried. I couldn't get the phone to show up with "adb devices" either, but that was working before I installed CM 10.1. This stuff is so finicky it's frustrating. I've wasted countless hours on three different phones over the past few years, but overall it's worth it to get a better OS.
VQ30DE said:
Yeah, had the phone in download mode and was using Odin 1.7. I have the latest Samsung drivers for WIndows installed, and when I mount the SD card the phone shows up properly. That guide you linked to was one I tried. I couldn't get the phone to show up with "adb devices" either, but that was working before I installed CM 10.1. This stuff is so finicky it's frustrating. I've wasted countless hours on three different phones over the past few years, but overall it's worth it to get a better OS.
Click to expand...
Click to collapse
I assume your running Odin with administrator privileges, if not try that. Maybe try flashing a different rom, a stable rom could fix the issue. Make sure USB debugging is checked, shouldn't affect Odin but worth a try.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
I assume your running Odin with administrator privileges, if not try that. Maybe try flashing a different rom, a stable rom could fix the issue. Make sure USB debugging is checked, shouldn't affect Odin but worth a try.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, tried running as admin.
I just tried Heimdall One-Click, and got the error they mentioned:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware.
You will need to use Linux to repartition with this firmware package. Install Ubuntu. In Linux, you can copy-pasta this into the terminal to correct the repartitioning problem and then flash bootloaders. http://forum.xda-developers.com/showpost.php?p=17485056&postcount=23
Click to expand...
Click to collapse
Seriously? I don't want to install Linux to flash this phone back to stock! No way to do this from adb in Windows or from within a rooted phone? Maybe I'll just return with with CM installed; the phone is basically a wifi device only unless the seller decides to change the IMEI and resell.
VQ30DE said:
Yeah, had the phone in download mode and was using Odin 1.7. I have the latest Samsung drivers for WIndows installed, and when I mount the SD card the phone shows up properly. That guide you linked to was one I tried. I couldn't get the phone to show up with "adb devices" either, but that was working before I installed CM 10.1. This stuff is so finicky it's frustrating. I've wasted countless hours on three different phones over the past few years, but overall it's worth it to get a better OS.
Click to expand...
Click to collapse
Try re-installing the driver for the phone.
I'm not sure if they changed it in the newer versions of CM but after a certain version you actually need the drivers for the Nexus S rather than the Vibrant for ADB to work properly.
(Someone correct me if this is no longer true)
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
firefly6240 said:
Try re-installing the driver for the phone.
I'm not sure if they changed it in the newer versions of CM but after a certain version you actually need the drivers for the Nexus S rather than the Vibrant for ADB to work properly.
(Someone correct me if this is no longer true)
Click to expand...
Click to collapse
Try here for the driver
3 most recent odin flashable bootloaders and modems For S5 G900T&T3 From 12/16 - 4/17
These were created from the stock roms and tested on my g900T using odin 3.11.2
So,if you want to update your bootloader and modem without having to flash the stock rom,then these are what you need.
Instructions:
Turn off your phone completely and manually boot into download mode.
Open odin 3.11.2,then plug your phone into your usb,and make sure odin sees it.
Load the bootloader into the BL tab of odin.
Load the modem into the CP tab of odin,and check the reboot
Hit start.....
The G900T will NOT work with the G900T3,If you need the G900T3 files,please download the right ones,towards the bottom of the page
As always,flashing is risky,so i am not responsible if you blow up your device..
G900TUVS1GPK3 Modem --> https://www.androidfilehost.com/?fid=529152257862710896
G900TUVS1GPK3 Bootloader --> https://www.androidfilehost.com/?fid=529152257862710897
G900TUVS1GQA2 Modem --> https://www.androidfilehost.com/?fid=673368273298939131
G900TUVS1GQA2 Bootloader --> https://www.androidfilehost.com/?fid=673368273298939132
G900TUVU1GQC2 Modem --> https://www.androidfilehost.com/?fid=745425885120722406
G900TUVU1GQC2 Bootloader --> https://www.androidfilehost.com/?fid=529152257862717494
(G900T3 ONLY) G900T3_GPK3_Bootloader--> https://www.androidfilehost.com/?fid=745425885120743020
(G900T3 ONLY) G900T3_GPK3_modem--> https://www.androidfilehost.com/?fid=889764386195910331
(G900T3 ONLY) G900T3_GQC2 Bootloader--> https://www.androidfilehost.com/?fid=817550096634777324
(G900T3 ONLY) G900T3_GQC2 Modem --> https://www.androidfilehost.com/?fid=673368273298962831
Here is the link to the Full TMB-G900TUVU1GQC2 stock rom.Extract the zip and load the md5 in CP tab of odin.
https://www.androidfilehost.com/?fid=673368273298945491
If i helped you out,please hit the thanks button
Good work Bro
Thanks
X_Mojahed said:
Good work Bro
Thanks
Click to expand...
Click to collapse
your welcome,glad you made use of them..
Thanks for this, i needed a way to update those without going the long way.
Jhfreeze said:
Thanks for this, i needed a way to update those without going the long way.
Click to expand...
Click to collapse
NP,i updated the long way,then decided to learn how to create these.Of course,i tested them on my own device first.If any newer ones come out,i'll make those and post them here also. Thanks
Are these from stock marshmallow roms?
SuperBrolySSJ said:
Are these from stock marshmallow roms?
Click to expand...
Click to collapse
Yes they are,all marshmallow.....
This is driving me nuts...I'm following the instructions. Odin is recognizing modem and my phone...but when I hit "start" it's giving me a "fail" message immediately after "now writing...please wait about 2 minutes" I've tried 3 USB ports and 3 cords. I have a 5.1.1 modem and can't flash to 7.x unless I update my modem to MM. I have no idea what to do.
DickyG said:
This is driving me nuts...I'm following the instructions. Odin is recognizing modem and my phone...but when I hit "start" it's giving me a "fail" message immediately after "now writing...please wait about 2 minutes" I've tried 3 USB ports and 3 cords. I have a 5.1.1 modem and can't flash to 7.x unless I update my modem to MM. I have no idea what to do.
Click to expand...
Click to collapse
Your using the G900T right??Are you running a custom rom?Try downloading the file again.Also,what odin version are you using?
bobbylo said:
Your using the G900T right??Are you running a custom rom?Try downloading the file again.Also,what odin version are you using?
Click to expand...
Click to collapse
Yes...G900T...currently running CM13.0 but would like to upgrade to one of the Nougat ROM's. My Odin version is 3.11.1...I know you call for 3.11.2...I'll download it if you think it will really make a difference.
Thanks...
DickyG said:
Yes...G900T...currently running CM13.0 but would like to upgrade to one of the Nougat ROM's. My Odin version is 3.11.1...I know you call for 3.11.2...I'll download it if you think it will really make a difference.
Thanks...
Click to expand...
Click to collapse
Yeah,try using Odin 3.11.2...Also,try turning the phone off,remove the battery for a minute,then boot into download mode.Also,are your USB drivers up to date on your computer?...If you can't get it to work still,you may have to flash the latest stock rom to get the modem and boot update,then just reflash TWRP,and restore your backup...
bobbylo said:
Yeah,try using Odin 3.11.2...Also,try turning the phone off,remove the battery for a minute,then boot into download mode.Also,are your USB drivers up to date on your computer?...If you can't get it to work still,you may have to flash the latest stock rom to get the modem and boot update,then just reflash TWRP,and restore your backup...
Click to expand...
Click to collapse
For some reason or another, Norton is kicking 3.11.2 off my computer...but I've even tried a newer version...3.12.3...still didn't work. I always do a battery pull before flashing and (according to Windows) my USB drivers are current. I thought about flashing a stock rom but that requires Odin and if I can't flash a modem, I certainly can't flash a ROM. Geez...the phone gods hate me!
DickyG said:
For some reason or another, Norton is kicking 3.11.2 off my computer...but I've even tried a newer version...3.12.3...still didn't work. I always do a battery pull before flashing and (according to Windows) my USB drivers are current. I thought about flashing a stock rom but that requires Odin and if I can't flash a modem, I certainly can't flash a ROM. Geez...the phone gods hate me!
Click to expand...
Click to collapse
Get rid of Norton,uninstall it...Its got to be norton....No one else has had a problem flashing these files...try uninstalling norton,then try again..Got to be something on your computer..What windows are you using?
bobbylo said:
Get rid of Norton,uninstall it...Its got to be norton....No one else has had a problem flashing these files...try uninstalling norton,then try again..Got to be something on your computer..What windows are you using?
Click to expand...
Click to collapse
Well, I tried disabling Norton...same result. Using Windows 10. The computer is new...Christmas present...but that doesn't mean its foolproof. Tomorrow I'm gonna download Odin and a couple modem files to my wife's laptop and try again. I think your instructions are fine...I've used every port and every USB cord I can find...maybe my computer has some sort of glitch...who knows.
DickyG said:
Well, I tried disabling Norton...same result. Using Windows 10. The computer is new...Christmas present...but that doesn't mean its foolproof. Tomorrow I'm gonna download Odin and a couple modem files to my wife's laptop and try again. I think your instructions are fine...I've used every port and every USB cord I can find...maybe my computer has some sort of glitch...who knows.
Click to expand...
Click to collapse
Well,can't speak for windows 10. don't like anything past windows 7. I run a dual boot windowsXP-windows 7 PC,I use the windows 7 to do all flashing.What OS is your wife's laptop? Let me know how it turns out.
bobbylo said:
Well,can't speak for windows 10. don't like anything past windows 7. I run a dual boot windowsXP-windows 7 PC,I use the windows 7 to do all flashing.What OS is your wife's laptop? Let me know how it turns out.
Click to expand...
Click to collapse
Failed again...tried on wife's laptop (windows 8.1)...made sure to use 3.11.2 and Samsung USB cord...recognized phone and failed as it always does...right after "writing...wait 2 minutes". Got to be a glitch in my phone somewhere and I don't think I want to go through the aggravation of doing a complete system wipe. I do have an old Dell desktop running XP in the closet...maybe I'll break it out and try it...but like I said, I think it's my phone. Thanks for all your help.
DickyG said:
Failed again...tried on wife's laptop (windows 8.1)...made sure to use 3.11.2 and Samsung USB cord...recognized phone and failed as it always does...right after "writing...wait 2 minutes". Got to be a glitch in my phone somewhere and I don't think I want to go through the aggravation of doing a complete system wipe. I do have an old Dell desktop running XP in the closet...maybe I'll break it out and try it...but like I said, I think it's my phone. Thanks for all your help.
Click to expand...
Click to collapse
I find it hard to believe its your phone...i don't think windows XP will work,Tryed it once,and its just too old of a operating system...If you know someone with a windows 7 computer,you can try that..Mine always works find when i boot into windows 7 and flash.Its very possible its those newer windows versions that are doing it..But i can't say for sure.Good luck with it,and let me know how it turns out.
You did try with all the modems and bootloaders i posted here,right?
bobbylo said:
I find it hard to believe its your phone...i don't think windows XP will work,Tryed it once,and its just too old of a operating system...If you know someone with a windows 7 computer,you can try that..Mine always works find when i boot into windows 7 and flash.Its very possible its those newer windows versions that are doing it..But i can't say for sure.Good luck with it,and let me know how it turns out.
You did try with all the modems and bootloaders i posted here,right?
Click to expand...
Click to collapse
I've let this sit for a few days and am pretty much out of options. I've used every port on my Windows10 desktop and wife's Windows 8.1 laptop...multiple Samsung cords (including the original one), multiple Odin versions, every posted modem. Windows says my drivers are up to date and Odin recognizes my phone every time. The only thing I can think of is that somehow my phone has developed a glitch..doesn't seem logical because it is working fine...but who knows. Have even tried to flash with Norton disabled, bluetooth disabled..and who knows what else. Not even thinking of trying to flash back to stock since I can't even flash a modem. But what about bootloaders? Have not tried to flash the comparable bootloader because I don't see how that effects the modem..but what do you think?
DickyG said:
I've let this sit for a few days and am pretty much out of options. I've used every port on my Windows10 desktop and wife's Windows 8.1 laptop...multiple Samsung cords (including the original one), multiple Odin versions, every posted modem. Windows says my drivers are up to date and Odin recognizes my phone every time. The only thing I can think of is that somehow my phone has developed a glitch..doesn't seem logical because it is working fine...but who knows. Have even tried to flash with Norton disabled, bluetooth disabled..and who knows what else. Not even thinking of trying to flash back to stock since I can't even flash a modem. But what about bootloaders? Have not tried to flash the comparable bootloader because I don't see how that effects the modem..but what do you think?
Click to expand...
Click to collapse
Yeah,What bootloader are you running?
bobbylo said:
Yeah,What bootloader are you running?
Click to expand...
Click to collapse
FOG6...same as the modem...came with the phone...supports 5.1.1. Haven't tried to flash the comparable bootloader yet because: 1. I never thought about it and 2. I figured if Odin didn't let me flash a modem, probably wouldn't let me flash a bootloader either.