Related
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Deenybird said:
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Click to expand...
Click to collapse
I use heimdall personally. Never had any problems with it. Do you have all the sgs2 drivers installed?
Also check md5 sums to make sure your download is ok.
Sent from my SGH-I777
I'll try heimdall. Drivers should be fine as kies is installed. Rom should be good as I've tried 2 different download sources
Make sure you install the libusb drivers for heimdall before flashing. The instructions are in the heimdall readme. Good luck
Sent from my SGH-I777
Just wanted to post that my problem is solved.
Summary: My AT&T Galaxy SII showed an error on boot (software upgrade failed. connect to kies...). Kies wouldn't even recognize the device so that route was a no go. So as everyone's recommended method of last resort, I decided to flash the device back to stock via odin. I entered download mode (volume up + volume down and plug in usb) and Odin would recognize the device, I would load the stock rom in the PDA slot and hit start and it would begin normally, but it would always fail after a few seconds on 'NAND write start', or 'factoryfs.img'. So I got a 1 click download solution using odin for reverting my phone back to stock. Same thing, it would recognize the phone, but stall out and fail. I also tried flashing clockworkmod via odin but and same problem. People recommended I try heimdall. It would recognize my device, and then fail after 'kernel 100%'.
I tried both programs on 3 different computers, and must have tried 12 different USB slots amongst all of them. I'm fairly handy with this stuff and I worked for hours on it.
xtra info: I had successfully used odin on my computer to flash a kernel just a week ago so I know my stock usb cable was working etc...
Resolution: So I hung my head and drove to the ATT store. After pressing a few buttons on the device and not getting anywhere they sent me to a nearby Device Support Center. I told the girl at the counter that my phone booted to this error screen and that connecting it to Kies did nothing. She asked if it was ok that in the case that she couldn't fix it she would offer me a replacement. I said that was fine and after 10 minutes in the back room she came out with a replacement (free of charge).
Well that was the good news. For the bad news, unfortunately I still don't know how to fix the problem I had, and don't really know how to avoid it in the future. I thought phone's could only get truly bricked if you messed with PIT files and such. There didn't seem to be anything more I could do than flash with odin or heimdall as those were already last resorts. I know I had the right files, the right drivers, and working usb. No matter how crazy I got with my iphone, a full restore was only a click away by plugging in to iTunes. Somehow I messed up my phone so bad that even the device support center couldn't fix it....? Shouldn't have had to be like that.
Thank yous: Thanks to ATT for having a walk-in store and for so easily offering up a replacement. Thanks to the many people on the web who offered remedies.
tl;dr - phone broke, att replaced, still a mystery
Im running stock Gingerbread, never been rooted.
What I am looking for is a simple one click method to root the phone for a few minutes so I can make a few tweaks and then unroot it.
Yes, Im aware that I can use the Odin method to root without tripping the flash counter, make my tweaks, and then use another Odin package to unroot it, however, there are a few problems with this, in order to keep this brief, I dont want to go into all the details but suffice it to say, I dont want root constantly enabled, I just want to enable it briefly and I dont want to install CWM so I can reset the flash counter and then (if its even possible) have to re-install the 3e recovery menu EVERY time I need root for something briefly.
Im looking for something along the lines of Super One Click (shortfuse.org) or UnlockRoot (www.unlockroot.com) where I can hit root, the phone reboots, I do what I need to do, hit unroot and the phone reboots unrooted. Both of these tools, needless to say, do NOT work (even tho they are listed as supported devices). Remember also, this is the ATT Note SGH-I717 so when looking thru the device lists supported by other software, make sure to look for the right Note .
i don't think those methods exist like they did with say the Samsung infuse. I used the Odin way, just as easy as super one click...but you mentioned you didn't want to use it so I'm not sure what you can do. Why not just stay rooted? And there is a flash counter reset just so you know
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I used odin super fast and easy
Sent from my SAMSUNG-SGH-I717 using xda premium
Im well aware of how easy the pre-rooted kernel is to flash via Odin, its the unrooting process that is a pain.
I dont want to stay rooted and I dont want to use Odin, the process of reverting back to unrooted is too much of a pain in the ass.
My guess is that there is no easy one click process or it would have been posted already.
Its a shame, one of the huge benefits with Android was how easy it was to gain root to tweak OS level things and then revert back to an unrooted state.
I used SuperOneClick without any issues whatsoever? What, is it not supposed to work or something?
juzz86 said:
I used SuperOneClick without any issues whatsoever? What, is it not supposed to work or something?
Click to expand...
Click to collapse
Erm, ok, Id love to know how you did...
First, what phone do you have (carrier). I am using the ATT Note.
If we are on the same page there, what settings do I need to enable on the phone and/or SuperOneClick?
On my phone, I enabled USB Debugging, in SuperOneClick, I left everything default, I click the Root button and on step 7 a bunch of gobbly gook appears (there is no log created so I cant just copy and paste some of the text) and it just stops. I left it sitting for a few minutes and nothing happened to either the phone or SuperOneClick.
littlewierdo said:
Erm, ok, Id love to know how you did...
First, what phone do you have (carrier). I am using the ATT Note.
If we are on the same page there, what settings do I need to enable on the phone and/or SuperOneClick?
On my phone, I enabled USB Debugging, in SuperOneClick, I left everything default, I click the Root button and on step 7 a bunch of gobbly gook appears (there is no log created so I cant just copy and paste some of the text) and it just stops. I left it sitting for a few minutes and nothing happened to either the phone or SuperOneClick.
Click to expand...
Click to collapse
I have two Notes. The N7000 I rooted using SoC on GB, doing exactly what you've done. The i717 was exactly the same. USB debugging enabled, plugged in and USB not mounted. MY computer is picky about USB ports so I use the same port and cable for every phone.
Grab the latest SoC (my sig has a link) and extract. Install Kies to get the USB drivers, then uninstall Kies and leave the drivers installed. Plug in the phone and let it install. Once it's done, run SoC (not as an administrator), select 'auto' for the exploit and click 'root'.
You'll get the usual 'found a gingerbread', 'sending 149 zerglings' etc. Then it tells you the 'overseer found a path' and after a few more steps reboots with root. Took me all of about 40 seconds.
I use AT&T phones unlocked in Australia, so we are using the same handset. This method doesn't work for ICS, you'll need to flash SU with CWM for that.
Let me know if I can help any more
Yea, unfortunately, it doesnt work for me.
I have the Samsung drivers installed (I know because when I plug in my phone under device manager, it shows my phone as correctly installed and I get a pop up from windows asking me whether I want to open a folder to browse the phones' contents - and Kies sees the phone).
I even tried uninstalling Kies but keeping the driver installed (Windows still asks me whether I want to browse the phone contents).
I also tried removing the sd card, altho this should not affect the process.
When I run SOC, I maximize the window so I can read the text and basically, when it gets to step 7, it sends 149 zerglings, then it waits 40 seconds, then it sends 189 zerglings, waits 40 seconds, then it says that it doesnt have write permissions and asks me whether I have root or not (not in a dialog box but in the text on the right hand side of the screen - I can only assume that it is initially trying to get a shell/temporary root so that it can do what it needs to for a permanent root), then it tries to push some files to the phone and then just completely stops. I let it sit for Id say 10 minutes with no progress.
The only thing that maybe is creating a problem is that the phone seems to be automounting, when I plug in the storage, it doesnt ask me what I want to do, it just mounts the device. I poked around in the settings and couldnt find any setting to disable this but Im not 100% sure this is a problem as the Captivate did the same, when you enabled USB debugging, it would automount the device.
Oh, and when I plug in the USB cable, the notifications bar shows 'MTP Initializing' and a few seconds later, 'MTP Mode'.
And Im using Super One Click version 2.3.3
littlewierdo said:
Im running stock Gingerbread, never been rooted.
What I am looking for is a simple one click method to root the phone for a few minutes so I can make a few tweaks and then unroot it.
Yes, Im aware that I can use the Odin method to root without tripping the flash counter, make my tweaks, and then use another Odin package to unroot it, however, there are a few problems with this, in order to keep this brief, I dont want to go into all the details but suffice it to say, I dont want root constantly enabled, I just want to enable it briefly and I dont want to install CWM so I can reset the flash counter and then (if its even possible) have to re-install the 3e recovery menu EVERY time I need root for something briefly.
Im looking for something along the lines of Super One Click (shortfuse.org) or UnlockRoot (www.unlockroot.com) where I can hit root, the phone reboots, I do what I need to do, hit unroot and the phone reboots unrooted. Both of these tools, needless to say, do NOT work (even tho they are listed as supported devices). Remember also, this is the ATT Note SGH-I717 so when looking thru the device lists supported by other software, make sure to look for the right Note .
Click to expand...
Click to collapse
Did you ever get a working solution to your question? I am in the same position: wanting to temporarily root my phone, do my tweaks and then re-root it so that I can run the POS enterprise mail application that has a policy to check for "root".
I would think that this should be much easier than it seems, but perhaps not
Thanks,
aus
I havent found any solutions yet...
SuperOneClick did not work for me either. I have used it on 3 other phones with no issue so I dunno.
Greetings,
My son has a Galaxy s2 running stock 2.3 which he bought in Singapore over a year ago, I think. He states that it has not been rooted. Over the last several weeks he has been getting the 'kernal panic upload mode' screen when the battery was getting low. Last week it became permenant regardless of the battery level. Yesterday I was able to talk him through entering recovery mode. He wiped the partition cache and rebooted with no apparent effect. A picture of the recovery mode screen idicates that the system was unable to mount /data (unknown error: 0). But it did show media files were copied succesfully. ... I've attached a picture of the screen. The phone is no longer recognized in Win7.
My basic question. How might we rescue the pictures and some text from the phone before redoing the os?
TIA,
Kim
Kim, flash siyah v5 and try cwm.
Also drill your son on what is that he did exactly, cause he must have done something.
Sent from the little guy
I had thought that if all else failed I would have him use Odin to re-apply his existing os. My thinking was that the file and partition structure would be close enough to what's there to allow normal usb connection and to d/l his pics and what not. Then I'd get him to install something with a little more support for recovery and snooping about. Decent enhancements!!
I don't know what he did other than I think he might have overloaded the little beast with too many apps constantly calling home on an older os. But, that's just a guess. Thanks for the upgrade suggestions. I'm only starting to research that aspect. I suspect that going direct to the better burns will be the way we'll end up going.
Be well,
Kim
Siyah is a custom kernel, no danger regarding existing data.
By flashing it you'll be able to access a temp recovery called clockwork mode.
Sent from the little guy
Greetings gastonw,
My son's getting the usb drivers from the Samsung site for the i9100. I found the tar Siyah-s2-v5.0.1.tar for Odin.
Odin3 version is 3.04. Don't know what else I need.
I'm going to be doing this long distance and I've not handled a smart phone personally so ...
1. Start the phone in download mode.
2. Connect phone to computer
3. Start Odin (making sure that Kies is not running), Odin should recognize the phone.
4. Load the tar in the pda section
5. check automatic reboot, and start.
6. I presume that I will know when it's done because odin will report success or finished, and the phone will boot.
To grab the data off this phone do we use the recovery mode or will it now be called clockwork mode?
At which point I presume we shut the phone down and do a normal start/boot.
Any thoughts would be appreciated. Thanks for your help. Reading the specs on the Siya work I'm almost tempted
to go get a phone for myself.
Be well,
Kim
Lol, that's awesome, your playing by the book
Custom recovery will become CWM instead of stock recovery.
And go ahead and get yourself a new phone, you're in for a hell of a ride.
Sent from the little guy
Thank!! My son called and said the usb still doesn't work. Hum .... I hope not, but I may be back to see if there's a way to transfer something from an sd card in order to save the data. On the flip side ...
Kim
Odin doesn't see his device or the pc calls it "unknown device"?
Can he get it to boot, he can use airdroid app or dropbox to transfer over wifi.
The custom kernel is just to get rid of that pabic message.
Sent from the little guy
Mornin' gastonw,
Well, as of a couple of minutes ago, win7 did not recognize the phone. Hopefully with a reinstallation of the Samsung specific usb drivers win7 and/or Odin will recognize the phone.
Interesting. When he booted into download mode the top of the screen said something like, 'Odin download mode'. Does this indicate that it might be rooted? To the best of my knowledge he was unaware of the three button boot loader mode and hence would not have changed the phone from the basic generic non-branded phone that he bought. Just wondering. If it is rooted is there a way to manually do, via the recovery mode, what Odin will be doing? It seems to me that if recovery allows to d/l from the sd card there must be a destination to be designated. I have no idea what the drive and directory layout is, and I'm a tad rusty on linix shell commands, don't even know what shell android uses. But, if I knew where the package had to go ... .
I'll write again when I know more.
Thanks again,
Kim
Well the last I heard is that no USB *and* it's probably a win7 problem!!!! Good golly miss molly!
Anyway, snooping about I found a thread [howto] which indicated that putting a clock work mod zip on an sd and d/ling it thru the recovery mode would install the clock work mod recovery boot.
http://forum.xda-developers.com/showthread.php?t=1814801
Now I can not find a further reference to a zip with the name format used in this post. However at the modclockwork site I do find two
http://clockworkmod.com/rommanager. One is for 'touch'. I don't know the difference between the two. But, am I understanding correctly that I can put the appropriate zip on an sd from which I can d/l thru the standard recovery mode which on restart I presume will give me access to cmw recovery mode? Seems to easy. LOL!!!
Any help would be appreciated.
Kim
This is how you root & flash cwm via recovery: http://m.youtube.com/#/watch?v=7psIQU69h3M&desktop_uri=/watch?v=7psIQU69h3M&gl=MX
Tell him to try another PC to see if it sees the device.
Genuine s2 usb I assume?
Sent from the little guy
I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Do you have the correct drivers installed? Does adb recognize the device? You're in Odin mode when you try to use Odin to push something? I believe with ME7 you can Odin back to the official stuff.
Sent from my SCH-I545 using Tapatalk 4
TheColdOne said:
I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Click to expand...
Click to collapse
You need to make sure you have the drivers for the phone and have a solid USB connection (I prefer the rear of a tower)
sent from my GE gs4
I ended up getting it to work. I had to go here:
http://www.intel.com/support/chipsets/inf/sb/CS-013541.htm
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
I hate to hijack a thread but I'm stuck here. My GS 4 (Vzw) was supposedly successfully rooted using TWRP, but now I have no way to enter any sort of recovery. The package I downloaded for the root does not have an Odin version to run. I've been getting the endless prompts to install the 4.3 update but there is no way to do this on my phone. I get the same "Could not do normal boot. Odin mode. Write protection enabled" message with the downloading screen. I try to boot into recovery via CWM or Goomanager but it always goes to the same screen. I can't make any backups or restore now either or I would just do a factory reset. Any ideas? I'm on VRUAME7.
Um.... there's no recovery available with ME7.... are you on the MDK bootloader?
Sent from your mom's smartphone
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
BoltsRUs said:
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
Click to expand...
Click to collapse
You're said that you're on ME7 - what you need to do is to flash the "No wipe" ME7 ROM onto your phone. It's in the Development forum.
http://forum.xda-developers.com/showthread.php?t=2301259
You've got to update to MI1 before you can install the 4.3 update (MJ7).
ONLY flash files intended for whatever release you're running. You can't mix and match, can't go backwards, and can't skip updates.
Theres also an ml1 factory image in the dev section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
TheColdOne said:
I ended up getting it to work. I had to go here:
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
Click to expand...
Click to collapse
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
nyankat said:
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
Click to expand...
Click to collapse
On that page I linked to, look for this:
Solution:
Download and run the Intel® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
TheColdOne said:
On that page I linked to, look for this:
Solution:
Download and run the Intel® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
Click to expand...
Click to collapse
Thanks! Finally Oden recognizes my phone
my amazing method
the same problem was with me 3-4 weeks ago...
follow the url-
dbloo dbloo dbloo dot autoroot dot chainfire dot eu
(i cant post the URL because the website is not allowing me.....understand and use the code)
1) choose your samsung model and download the recovery file
2) download and open odin on a dekstop
3) connect your device to the dekstop
4) press the volume down, home button and power button together till the screen changes
5) press the volume down button again
6) odin will show the message "attatched or connected"
7) click pda
8) attatch the file you downloaded
9) your device will be fixed and will be restarted
ur welcome
hai i am stuck at download mode with message as could not normal boot how to fix it
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
muddled said:
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
Click to expand...
Click to collapse
Hey Mate,
Firstly we all are noobs here helping each other, secondly from my experience of S3, it is such a device that under any condition, if your hardware is intact, you can recover your phone from almost anything, so yeah you might have a solution to your problem.
Coming to the problem at hand, i had the same thing happen to my S3, (only twrp logo showed, couldn't access recovery, no ROM, only download mode available) the way i fixed it was using odin, now i know you say that odin is not recognizing your device, the thing is firstly Kies is useless in this situation acc. to me, it only works stock ROM and that too with difficulty, what i would say is go here - http://developer.samsung.com/technical-doc/view.do?v=T000000117
and then install the drivers to your PC, next up download the official firmware from sammobile or any other site (careful of the version you are using), now put the phone in download mod, start odin and then connect your phone. Now, hopefully odin will recognize your phone and you can flash the official firmware, also i would recommend to stay on the official firmware for like a week before returning to flashing again as i have noticed that constant flashing and wiping leads to not only errors like "unable to mount EFS" but also serious errors like "Unable to mount /system" or "Unable to mount /Data" ,which clearly sucks
Please try the method and tell me if it worked , if not we'l try something else but we sure as hell will get your device working again
If still not recognized then here is a suggestion :
Exit/uninstall from nokia/ovi suit.
Exit/uninstall bluestack. (if u r using it)
Update your drivers(phone specific)
Use correct odin version acc to ur phone
Sent from my Micromax E352 using XDA-Developers mobile app
I'm just gonna throw my 2 cents in too. I didn't read your whole thread as I'm in a slight rush right now.
But basically -
Can your PC recognise your phone when it's plugged into USB in Download Mode? If so, use ODIN to flash any stock firmware and you're back to square one (working, but stock) phone. Then go from there. Obviously try to flash the right firmware or you'll end up no further forward.
If it can't recognise it, try reinstalling the drivers, uninstalling the programs mentioned above and using another USB cable. My experience with my own S3 has shown potential wear with the USB port on the bottom of the phone presumably due to it's age and as a result it doesn't recognise many USB cables.
Regards