Related
I have done some good search on the forums but my issue seems to be unique. tried upgrade o Froyo, got stuck on Vibrant screen after reboot. Tried using Odin to stock, it all works fine, I can go into download mode, start odin, pick up pit and T959UVJFD.tar file, odin does its magic, everything passes.... phone reboots doest the installation and reboots again... now it gets stuck to Vibrant screen.
Cant pass this, have tried multiple stock roms from various source... what am I doing wrong ? Please help
sankalpkohli said:
I have done some good search on the forums but my issue seems to be unique. tried upgrade o Froyo, got stuck on Vibrant screen after reboot. Tried using Odin to stock, it all works fine, I can go into download mode, start odin, pick up pit and T959UVJFD.tar file, odin does its magic, everything passes.... phone reboots doest the installation and reboots again... now it gets stuck to Vibrant screen.
Cant pass this, have tried multiple stock roms from various source... what am I doing wrong ? Please help
Click to expand...
Click to collapse
Did you try 3 button to get into clockwork.if you can, try a different kernel.its not bricked, if there is any good news.one of these smart people in the vibrant community will help.
Sent from my GT-I9000 using XDA App
I can get into recovery using the 3 button, its not the clockwork recovery though, also not sure how to apply any other kernel as I can't access the internal SD memory.
Did you check re-partition in Odin? (Be careful though!)
yes tried with and without re-partition.
Yikes. When you say you've tried multiple stock ROMs, you mean you've used Odin versions of several stock ROMs?
inconceeeivable said:
Yikes. When you say you've tried multiple stock ROMs, you mean you've used Odin versions of several stock ROMs?
Click to expand...
Click to collapse
No I meant I have downloaded the stock Rom from multiple websites and none of them worked.
Did you back your rom with clockwork?
Hanir said:
Did you back your rom with clockwork?
Click to expand...
Click to collapse
Nope, but the problem I believe is that I wont be able to install clockwork anymore as I can't access the internal SD card, is that correct ?
If you can get to stock recovery, I'm pretty sure you can push files to the internal sd storage via adb.
Sent from my SGH-T959 using XDA Premium App
inconceeeivable said:
If you can get to stock recovery, I'm pretty sure you can push files to the internal sd storage via adb.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Not sure how to do it, but I'll do some reading and give it a shot.
You seem kind of new so just asking this in case, you aren't using a galaxy s 4g are you?
If you are using the vibrant, then disregard the first line of this post.
Try some of these things:
Right drivers installed?
Try another version of odin.
Make sure you are using the usb cable that came with the phone.
I've always heard using a usb 2.0 port is recommended.
Sometimes I've found using a different computer seems to solve the problem. (preferably 32bit)
Good luck.
ferhanmm said:
You seem kind of new so just asking this in case, you aren't using a galaxy s 4g are you?
If you are using the vibrant, then disregard the first line of this post.
Try some of these things:
Right drivers installed?
Try another version of odin.
Make sure you are using the usb cable that came with the phone.
I've always heard using a usb 2.0 port is recommended.
Sometimes I've found using a different computer seems to solve the problem. (preferably 32bit)
Good luck.
Click to expand...
Click to collapse
I am using a vibrant, and yes I am not using the cable that came with the phone, I lost that one using another over the counter cable. I have tried a Win XP and Windows 7.0 PC. One thing I have noticed is that on my PC I always get a notification that "your device can work faster if connected to a usb2.0 port" I get that message to all the ports on my laptop. Maybe its the cable.... not sure if a cable can make it work usb1.1 when the port maybe really usb2.0.
thanks
Sounds like Odin is working fine. Did you try Delete All User Data (or whatever it's called) in stock recovery?
flash eugene's froyo that doesn't brick then stock JFD. solves the problem in most cases.
german103 said:
flash eugene's froyo that doesn't brick then stock JFD. solves the problem in most cases.
Click to expand...
Click to collapse
Thanks but I tried that as well.. no luck
inconceeeivable said:
Sounds like Odin is working fine. Did you try Delete All User Data (or whatever it's called) in stock recovery?
Click to expand...
Click to collapse
yep tried the option delete all user data. I have been under the impression that if you can get into download mode you havent bricked your phone and it can be recovered.
is there a way I can access the internal SD card and format it manually and transfer the roms / clockwork recovery to it ?
sankalpkohli said:
is there a way I can access the internal SD card and format it manually and transfer the roms / clockwork recovery to it ?
Click to expand...
Click to collapse
Do you have adb installed and setup? If not, find a tutorial and get it working.
Once you have adb working, this should work:
1. Boot phone into recovery with 3 buttons
2. Select reinstall packages. (Yes, it will fail, but this step is necessary for some reason)
3. From your PC, execute "adb push update.zip /sdcard" (This is assuming you have the update.zip from Clockwork Recovery)
4. Select reinstall packages again, phone will reboot, select reinstall packages again
inconceeeivable said:
Do you have adb installed and setup? If not, find a tutorial and get it working.
Once you have adb working, this should work:
1. Boot phone into recovery with 3 buttons
2. Select reinstall packages. (Yes, it will fail, but this step is necessary for some reason)
3. From your PC, execute "adb push update.zip /sdcard" (This is assuming you have the update.zip from Clockwork Recovery)
4. Select reinstall packages again, phone will reboot, select reinstall packages again
Click to expand...
Click to collapse
C:\AndroidSDK\tools>adb push init.rc init.rc
failed to copy 'init.rc' to 'init.rc': Permission denied
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
Hey I have a i9100 that I had running on cm9 nightly. I updated my phone to the latest one at the time which was jul 22 and was 101.56 megs I believe. I went into cwm to install the firmware, wiped user data then installed the update. Install went fine, no errors in cwm. Although when I did wipe data I did not wipe cache with it.( I just wiped data accidentally because it was a force of habit since I flash alot)
Now the phone is in a boot loop. It won't go into recovery mode but will do download mode. Although when it is in download mode windows is saying that the device is malfunctioning. The setup I'm using is the same I've used to flash the phone atleast 30 times via oden so it should be working in theory.
Any ideas guys, I'm at the end of my rope as far as what to do.
Read this and see if that can help you
http://forum.xda-developers.com/showthread.php?t=1457458
That's the First thing I read when I searched for a solution. But that relies on the computer seeing the phone, which mine doesnt. It's looking like jtag may be the route I have to go. Any have any experience with those services
infuse4g said:
Hey I have a i9100 that I had running on cm9 nightly. I updated my phone to the latest one at the time which was jul 22 and was 101.56 megs I believe. I went into cwm to install the firmware, wiped user data then installed the update. Install went fine, no errors in cwm. Although when I did wipe data I did not wipe cache with it.( I just wiped data accidentally because it was a force of habit since I flash alot)
Now the phone is in a boot loop. It won't go into recovery mode but will do download mode. Although when it is in download mode windows is saying that the device is malfunctioning. The setup I'm using is the same I've used to flash the phone atleast 30 times via oden so it should be working in theory.
Any ideas guys, I'm at the end of my rope as far as what to do.
Click to expand...
Click to collapse
No CM9 nightly is 101.56MB. They are usually around 130MB. You probably flashed a CM7 nightly. AS long as download mode is working, you can flash resurrection and then the correct nightly.... or odin back to stock, root... then flash the nightly, but make sure you have the correct version as the CM7 and CM9 nightlies appear in the same list and it's easy to grab the wrong one if you aren't careful.
donalgodon said:
No CM9 nightly is 101.56MB. They are usually around 130MB. You probably flashed a CM7 nightly. AS long as download mode is working, you can flash resurrection and then the correct nightly.... or odin back to stock, root... then flash the nightly, but make sure you have the correct version as the CM7 and CM9 nightlies appear in the same list and it's easy to grab the wrong one if you aren't careful.
Click to expand...
Click to collapse
Thanks that is what happened. Now I have to pick up the pieces
infuse4g said:
Thanks that is what happened. Now I have to pick up the pieces
Click to expand...
Click to collapse
I figured that's what it was. It could be much worse though. Let me know if you need more help.
donalgodon said:
I figured that's what it was. It could be much worse though. Let me know if you need more help.
Click to expand...
Click to collapse
Both the computers that I have Won't talk to the phone when it is in download mode. I have windows 7 and 8 and neither want to be friends with my phone. I am killing kies before I start Odin. windows says the the device is malfunctioning. Any ideas?
infuse4g said:
Both the computers that I have Won't talk to the phone when it is in download mode. I have windows 7 and 8 and neither want to be friends with my phone. I am killing kies before I start Odin. windows says the the device is malfunctioning. Any ideas?
Click to expand...
Click to collapse
Do you have the drivers installed? If so, and it's still not working, you might try a different USB port and/or cable combo to see if one of them could be wonky.
donalgodon said:
Do you have the drivers installed? If so, and it's still not working, you might try a different USB port and/or cable combo to see if one of them could be wonky.
Click to expand...
Click to collapse
could it be that flashing cm7 on cm9 damaged the usb functionality. but the phone is still recognizing the jig that i have. the phone will go into download mode via button combo or jig. since the jig still works doesnt that mean that the usb port on the phone is still functional
HELP! Bricked Galaxy S2- GT-i9100
I have a galaxy s2 gt-i9100 and i love this phone but it's been bricked and i want to know if theres anything i can do. I was running cm10 no problem for awhile now even though one of my flashes took away my computers ability to see my phone when plugged in and i've tried everything. I thought mobile odin was what i was looking for to flash the official JB that came out. so i flashed it and then that was all she wrote for my phone. won't turn on at all i just see a greyed out battery on my screen.
i can get into download mode using button combos no problem but odin doesn't recognize just like computer.
I can get into recovery mode but it's not the same as when cm10 was on i think it's stock recovery from when i tried to flash with mobile odin and the options it shows me do not help me at all.
my question is: can i save my phone? or do i have to buy a new one?
P.S. It must be the phone cause i'm using a new computer and it can't see the phone either, i downloaded kies and when i plug in the phone it still goes through the process of finding and trying to DL the drivers but then it fails. same as my computer.
please and thank you
paul
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 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