If someone could help me I would be forever grateful. I got my AT&T GS3 yesterday and today after a LOT of hesitation I decided to see if I could root it. I couldn't find a lot of helpful resources and I ended up at the guide found at galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/. I was somewhat afraid because the guide refers to the I9300 but mine is the I747 and it turns out that fear was justified. Odin says FAIL with an ominous red background and says the following:
Code:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
After that I looked at my phone's screen and it had a short message in red that said "Unsupport dev_type". Now when I turn on the phone I am greeted by the ODIN MODE screen and a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
At this point I don't have critical data that can't be restored though I would love to not lose my data anyway. I am much more concerned about being able to boot my phone again. Is there any hope or am I totally screwed?
Search Chainfire thread here to see if your device is supported for rooting
http://forum.xda-developers.com/showthread.php?t=1695238
For official firmware and guide (and also rooting) try Intratech thread here:
http://forum.xda-developers.com/showthread.php?t=1671969
Sent from my GT-P6810 using XDA Premium HD app
I wish I had found that thread via my google searches before I attempted to root. I am certain that there is no working root right now for my I747. I am really hoping there is something else I can do to get my phone working again. At least my phone works in odin/download mode still. I just hope there is some way I can fix whatever the cf root did to my phone. Any further suggestions?
Reinstall official firmware and then make a backup and flash the correct I747 root. nothing from I9300 will work with your model
Sent from my GT-I9300 using xda premium
Get the official firmware from the link posted above and flash it via Odin.
when the Sgs2 was release last year for att I accidentally flash the International (I9000) on it so I know how you feel
Sent from my GT-I9300 using xda premium
Dang...guess I'll just have to wait for a firmware to be posted for mine. Unfortunately there is no stock firmware released yet for mine. I just found this thread as well where others have done the same thing inadvertently and are also waiting for a stock boot.img: http://forum.xda-developers.com/showthread.php?t=1703488&page=19
possible solution
I don't know if this will help but i managed to get out of the same situation. After getting the error the phone would boot and tell me to fix w Kies. I found that if I took the battery out for a while then started it back up using vol down and home button then plugged phone in after the warning, and hit volume down my phone telling it to reboot and it started up no problem.
You know there is a forum for the AT&T version right? There is a rooting guide there. ALWAYS make sure that you are using the root method for the RIGHT model of phone before you do anything.
Go the to the XDA main forum page. Scroll down to the bottom and you will see the AT&T GSIII forum areas.
Thanks to the work of several people who did the same thing I was able to recover the stock boot.img. For anyone else who lands on this thread, you can find a stock boot and instructions at http://forum.xda-developers.com/showthread.php?t=1727443.
Baldilocks, I will always make sure to go there from now on. Usually I haven't been much more than a casual lurker of the forums so I wasn't aware of that but I've learned my lesson. Thanks everyone!
v0rtex said:
Thanks to the work of several people who did the same thing I was able to recover the stock boot.img. For anyone else who lands on this thread, you can find a stock boot and instructions at http://forum.xda-developers.com/showthread.php?t=1727443.
Baldilocks, I will always make sure to go there from now on. Usually I haven't been much more than a casual lurker of the forums so I wasn't aware of that but I've learned my lesson. Thanks everyone!
Click to expand...
Click to collapse
I try everything, with several boots, odin versions, etc. The main problem was the usb . It works without problem with the new one usb.
Related
Hello everyone!
First of all, let me start by thanking everyone for such a wealth of information here on XDA Developers! And a big thanks goes to all the devs who worked so hard to provide us with some wonderful tools/apps and help as well!
Now, my problem is that I am a complete noob. I tried my best to do some research before I could start playing around with roms and what not. I rooted my Samsung Galaxy VIBRANT and after rooting it, I wanted to install the Voodoo lagfix. I used the instructions available here. After that, the phone stopped working in a way that it kept going back to Recovery Mode. Every time I had to select REBOOT option only to end up in Recovery Mode again.
I then tried to use ODIN to get back to stock as it made most sense. I downloaded the files by following this link http://forum.xda-developers.com/showthread.php?t=734475&highlight=stock+JFD and followed the instruction. Odin successfully finished the task and then my phone rebooted and the glorios Samsung GALAXY S logo appear but after that everything goes dark and by everything I mean everything but the 4 touch sensitive buttons. They are lighting up but the screen doesn't work.
Naturally, I didn't panic because from what I have read here, it is very difficult to brick the phone as ODIN appears to always come to rescue. The thing is that it just doesn't move forward.
After a while, I started to panic and then I following this link http://forum.xda-developers.com/showthread.php?t=1047087 and download the files again and followed all the instruction but with same result.
Here is the ODIN log
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.rfs
<ID:0/008> modem.bin
<ID:0/008> factoryfs.rfs
<ID:0/008> dbdata.rfs
<ID:0/008> param.lfs
<ID:0/008> zImage
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
After ODIN is done doing it's thing and the phone reboots, it says "Data Wipe Failed" just for a second before it boots to the Galaxy S logo screen. Afer this, it goes dark.
Guys, have I done the almost undoable? Have I just bricked my phone? I tried to search for this problem but maybe I suck at it and couldn't really find anything very useful and related to my problem so I decided to start a new thread. I apologize if I should have tried some other keyword to get better search results but believe when I say that I really did try.
There are thousands of brilliant android minds here and I am dead sure that someone will help me out of this grave situation and save me from using my old Nokia 5800 XM again!!!
Thanks again,
Z
Try these 3 methods!!
aio toolbox
usb jig
or
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper tar file in pit and the .pda file in pda in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
Thank you for your answer. I have already tried the ODIN method to no avail. The phone screen is still black while the touch sensitive buttons are on. I have no idea what the following are
aio toolbox
usb jig
And I am going to take a look at it. While I do that, could you please tell me if you think that I have bricked my cellphone already?
zee.syed said:
Thank you for your answer. I have already tried the ODIN method to no avail. The phone screen is still black while the touch sensitive buttons are on. I have no idea what the following are
aio toolbox
usb jig
And I am going to take a look at it. While I do that, could you please tell me if you think that I have bricked my cellphone already?
Click to expand...
Click to collapse
I don't think the toolbox will help you
http://forum.xda-developers.com/showthread.php?t=954509
http://www.mobiletechvideos.com/blog/?tag=jig
the later you can go to youtube and see it in action
Thank you everyone for your help! I kept searching and searching and I finally found the solution. Here is what I did...
Follow this link: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Download "Froyo That does not Brick" HERE
Download "True Stock 2.1 firmware for Vibrant" from HERE
Follow the instruction posted HERE
Remember that after the first step, you WILL see error in recovery mode. Do not panic and take out the battery and proceed with Step 2 and that'll help you. I hope this will help.
Now, I have another question. Can is it safe to ROOT my phone again? If it is, what method should I use since I am back on Eclair?
Thank you,
Zee
zee.syed said:
Thank you everyone for your help! I kept searching and searching and I finally found the solution. Here is what I did...
Follow this link: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Download "Froyo That does not Brick" HERE
Download "True Stock 2.1 firmware for Vibrant" from HERE
Follow the instruction posted HERE
Remember that after the first step, you WILL see error in recovery mode. Do not panic and take out the battery and proceed with Step 2 and that'll help you. I hope this will help.
Now, I have another question. Can is it safe to ROOT my phone again? If it is, what method should I use since I am back on Eclair?
Thank you,
Zee
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=849028
get the update.zip from there and put it on sd (16gb)
go to recovery reinstall packages
reboot and done
get rom manager off market and flash clockwork recovery choosing vibrant if you want to flash roms
Hello,
I have an International (or UK I guess) Galaxy S3, Model No.: GT-I9300. One day it wasn't responding, so I took the battery out and put it back in, and when I restarted it, it got stuck at the boot screen indefinitely. I tried going to the Recovery Mode to do the factory reset but it wouldn't respond to that (Many people have tried), but I can go into Download mode however.
My first question is what could this issue possibly be, where it doesn't respond to going into Recovery Mode, but still Download mode works? Is flashing the phone likely to fix the issue? I've searched this forum but couldn't find anything that seemed close to my issue. The phone has never been rooted and is running the most up to date stock ROM that I could get from Kies (Well, I ran a firmware update a few months ago using Kies and it's been working fine since then)
So I thought that reflashing it with the stock firmware using Odin would solve my problems. I found this link on the wiki which led me to this thread on the forum. So I have set up my machine to follow those instructions with the UK stock rom which in the thread is detailed as
XXALE8
Firmware Info
PDA: XXALE8
Phone: XXLE8
Date: 13/05/2012
Android Version: 4.0.4
where I selected the BTU link below it.
I was about to start the flash, but then my friend who's on xda all the time said that he saw threads with people who've been having problems with the International S3 with Odin. I've searched and found nothing. It seemed unlikely but I figure I should make a post to get the opinion on this.
Have there been issues with using Odin with the International Galaxy S3? Is there anything that people recommend that I be certain that I do before attempting this?
EDIT: I tried it and got this message:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
It's often file permission error, fix it with cwm recovery.
Howto in stiky threds. Nwm did not ser the pit stuff.
Sent from my GT-I9300 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1760683&page=2 seems to have happened to others google the fauld to see what you can find?
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
Hi,
I've looked everywhere to solve this problem but with no solution.
Yesterday I decided to flash my firmware from the leaked Jelly Bean from last November to the stock ICS in order to have my phone back to the normal update way.
However, when I try to flash with Odin, it gets stuck and has this:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I have PhilZ Touch 3 on the phone and chose "Clean Before Flash New ROM" in recovery. Problem is that this didn't help with Odin and now my phone just sits on the "Samsung Galaxy SII GT-I9100" screen and doesn't move.
Apologise for my noobishness
The 'Odin doesn't work' thing gets covered more times in a week than pretty much anything else on here. You need to search for/read those threads & find the set list of troubleshooting steps you need to try & keep trying those until the flash works. It is almost always (in 99.99999999999999999999999% of cases) something very simple/obvious not being done or being skipped that causes the flash not to work.
MistahBungle said:
The 'Odin doesn't work' thing gets covered more times in a week than pretty much anything else on here. You need to search for/read those threads & find the set list of troubleshooting steps you need to try & keep trying those until the flash works. It is almost always (in 99.99999999999999999999999% of cases) something very simple/obvious not being done or being skipped that causes the flash not to work.
Click to expand...
Click to collapse
Yeah thanks. I've looked over and found a whole list on here such as try different computer, different ports, run as admin etc etc and they didn't work after trying them over and over. They seemed quite generic :crying: I thought it might have been a problem with the fact that PhilZ is on there. Or should that not make a difference?
JackJack94 said:
Hi,
I've looked everywhere to solve this problem but with no solution.
Yesterday I decided to flash my firmware from the leaked Jelly Bean from last November to the stock ICS in order to have my phone back to the normal update way.
However, when I try to flash with Odin, it gets stuck and has this:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I have PhilZ Touch 3 on the phone and chose "Clean Before Flash New ROM" in recovery. Problem is that this didn't help with Odin and now my phone just sits on the "Samsung Galaxy SII GT-I9100" screen and doesn't move.
Apologise for my noobishness
Click to expand...
Click to collapse
Did you install KIES PC software? If yes, try following:
On your PC:
ctr+alt+del > start task manager > processes > find all processes with "kies" in their names (there should be two or three running) > kill all of them.
Then try odin again.
Whatever firmware (rom or kernel) you currently have on the phone is irrelevant/won't affect anything you try to do in download mode.
That advice is generic for a very good reason. In the overwhelming majority of cases where this happens, it's one of those steps not being done (or people saying they've 'tried everything' when they haven't). You haven't said anything to indicate your case is any different, I would suggest you find an actual thread that has all the steps listed rather than just a couple of them (Immortalneo was the last person to list the lot of them recently, search his posts); there's about 10-12, and keep trying them. That's the only way you're fixing your phone.
Many40 said:
Did you install KIES PC software? If yes, try following:
On your PC:
ctr+alt+del > start task manager > processes > find all processes with "kies" in their names (there should be two or three running) > kill all of them.
Then try odin again.
Click to expand...
Click to collapse
Yeah I tried that to. I removed the Kies and KiesTrayAgent. Still no luck
MistahBungle said:
Whatever firmware (rom or kernel) you currently have on the phone is irrelevant/won't affect anything you try to do in download mode.
That advice is generic for a very good reason. In the overwhelming majority of cases where this happens, it's one of those steps not being done (or people saying they've 'tried everything' when they haven't). You haven't said anything to indicate your case is any different, I would suggest you find an actual thread that has all the steps listed rather than just a couple of them (Immortalneo was the last person to list the lot of them recently, search his posts); there's about 10-12, and keep trying them. That's the only way you're fixing your phone.
Click to expand...
Click to collapse
Okay thanks for that. I'll check that out. And thanks for clearing up about the current firmware to. Makes me feel a bit more relieved :fingers-crossed:
JackJack94 said:
Yeah I tried that to. I removed the Kies and KiesTrayAgent. Still no luck
Click to expand...
Click to collapse
OK, then just follow the advice given already by MistahBungle (you must have missed something)
BTW what is exactly firmware you are trying to flash, is it made for your device, might be bad download ....
Dear XDA'ers,
I know their are a lot of topics on this problem, but I can't seem to find the answer.
The first thing I tried was going into recovery mode and doing a factory reset. That did not do the trick.
After that I wasn't able to get into recovery mode anymore, so I went online and searched some topics.
I downloaded a stock S2 ROM and flashed it through ODIN, but it kept failing.
From searching topics it seemed like my S2 suffered from NAND rw corruption.
And nothing fixed, so eventually I went to flash the bootloader. This was the first flash that was succesfull and it got me back to the samsung home screen. Then I tried to flash a new 3 part stock ROM, but it is not working, it keeps getting stuck at this point.
Any one that can talk me through this? Have not a lot of experience with this, so please try to keep it simple for me.
Thanks in advance
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
MistahBungle said:
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
Click to expand...
Click to collapse
but if that would be stuffed. I shouldn't be able to flash a bootloader should I?
You're the one who mentioned NAND corruption.
If the NAND really is corrupted, then that's the fix. And no, 'successfully' flashing a bootloader (or anything) does not necessarily mean the phone is easily fixable. 'Success' in Odin without the phone working/booting normally isn't success at all.
As per my previous post, find the thread (which really is the reference of these things here), try the stuff in it, see if you can fix it.
If not, you know what to do.
same problem bootlooping
hi guys i am currently having the same problem, i successfuly flashed the JB stock firmware but it's still keep bootlopping..my combo button doesnt work so i am using USB JIG to go into donwload mode, i can even go to recovery mode..hoping for some can link me or provide with FULL PACKAGE, meaning it has a PIT file, BOOTLOADER, CSC, PDA AND PHONE..I think this will be my last resort, so if anyone having this file im looking for plz plz plz direct mo to tha..thnaks
yes u have emmc corruption I have fixed it
but my fix was for data partition your problem is the kernel partition ill make a fix for your phone and inform u soon
Sent from my GT-I9100 using xda premium
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
iamtalha said:
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No luck .
Stuck at NAND WRITE:
Log:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!