guys im having a problem with odin
i connect the s2 and want to flash stock 4.1.2 i9100XWLSD and put the phone in download mode ,, pda etc ( u know)
then i get this error in odin ,, and i have flashed this exact md5 on another s2 and it work
what should i do now ?
Keep trying. There's a bunch of troubleshooting steps to work through when an Odin flash fails. As you've managed to successfully flash onto another s2, you can probably eliminate a few of the possible causes. Search on here for the steps, I know I've posted them not too long ago, and MistahBungle has also posted them multiple times.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
wanna post what's the error that odin gives you?
Most likely misplaced files in Odin
IceCreamSandwhich ( LorD ClockaN ) S-OFF DHD
I just had the same problem. I flashed the CM resurrection version, worked then I wanted to try something else and the thing would just fail right in the same place it failed for you. I had Odin3_v3.04 and decided to try a different odin so i tried Odin3_v1.85
I see you are running odin3_v1.85 so I reckon you should just download any other version of odin and give it a go...
Related
Hello! I'm really interested in trying Litening's ROM and I've tried multiple times. I've followed the instructions EXACTLY as written. I searched around the forums and also tried running the Kernel Cleaning Script before flashing but to no avail.
No matter what I do, after Odin finishes flashing, my SGSII boots up to the dreaded Kernel Panic Upload mode....
The ROM from which I'm trying the Litening ROM flash is ICS 4.0.3 XXLPB.
Please help and thanks!
One download a new copy .
That fails try a different rom .
jje
sometime it happened to my phone also.
not with specific rom,but i happened.
If coming from ginger,did u update your bootloader,if not flash with 512 pit file and tick repartition,then flash with Odin
Right way to flash with Odin
1 open Odin
2 set the files(rom)in Odin
3 reboot phone into download mode(fully recharged battery
4 connect to odin
5 wait for for Odin to confirm your phone(03 or 07) and flash
6 phone reboots...done
Kernel panic uplod mod
This is really a PAIN giving PANIC now....
People who flashed freshly ICS rom including Bootloade have also got this PANIC,
I have never flashed an ICS rom from ODIN, flashed ICS from CWM on my GB, I have got once since I installed 2 days back....
I was thinking that, this virus was spread from leaked ICS version but no, this PANIC is there from 2010, people who upgraded from 2.3.3 to 2.3.5 also had got this...
ONLY SAMSUNG KNOWS WHY THIS IS HAPPENED
it is not caused by any KERNEL,
it is not caused by any Bootloader
it is not caused by any version of firmware
something somwhere a mismatch between firmware and hardware happens...
Only a remedy for this issue is to Keep on changing the ROM until you get the one without this issue.....
Thanks to all for your replies.
I indeed downloaded a fresh copy, also tried different versions, same result.
ZACQ8, I actually read another reply you posted somewhere else about flashing stock GB first then trying to flash the Litening ROM, haven't tried it yet, but will try it and then report back.
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
dingo dog said:
Hi. This probably wont help, but try to use fresh odin download and other pc with new drivers installed without Sam Kies. older versions of odin did not worked with mine s3 and I had green screen while flashing problems when I used my old laptop to flash. Fresh pc with fresh drivers did the trick
Click to expand...
Click to collapse
Hi - Thanks for the tip, but I already tried with my wife's laptop. Should have mentioned in the original post.
Thanks again.
Older versions of Odin do work on SGS3 .
evelopment where I thought it should go but I haven't posted at all before so it won't let me.
Development only posts not Q&A nothing to do with 10 posts .
Two thoughts could be the usual flashed multiple stuff and phone is confused plus wrong PIT file flashed .
Thats just firmware not hardware problem .
Or indeed at some stage Nand is corrupt .
Solution would be
Try correct PIT file first before a repair centre .
jje
Just wanted to say that I have the same problem, but mine is even more strange. I can boot into the system but I have to disable wifi and mobile data right away otherwise the phone will reboot after a couple of seconds. I see the phone if I connect it to the computer but I can not write or read the files on the phone. But I tried the toolbox and could push an apk to the phone.
CWM works but if I try to wipe or flash another rom it reboots, some stuff works and other just reboots the phone.
Download-mode works and Odin finds the phone but everything I have tried fails. I have tried standard stock firmware, 3 part firmware and PIT but it always hangs on NAND Write.
If anyone has some solution I would be thrilled.
Bananafische said:
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable
My problem:
[*]Won't boot into recovery
[*]Will boot into download mode
[*]Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
[*]Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
Thanks
Click to expand...
Click to collapse
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Try this process: Samsung Galaxy S3 Not Booting? Here’s The Solution You can get detailed instructions here and that .PIT file too.:angel:
Click to expand...
Click to collapse
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
I am glad that It worked for you
I am still stuck, I am guessing that if none of the PIT´s work then it is officially bricked?
u didn't try the link posted by me?
theonlyanil said:
u didn't try the link posted by me?
Click to expand...
Click to collapse
it dosen't work ,stop at Get PIT for mapping..
help me
Hy guys Im from Hungary and i would like to flash my i9300 tmobile phone. My question is: can i flash the poland xeo to it or i just have to wait for the official tmobile rom? Thank you!
Where did you got the pit file
Bananafische said:
It worked!
PIT flash successful, then stock rom restored
I still needed to go in to stock recovery and do a factory reset from there to undo the encryption.
Thanks so much for everyone's help.
Click to expand...
Click to collapse
Where did you got the pit file
Hello, the PIT Flash didn't work for me either.
I was CF-rooted while overseas and stupidly forgot to disable auto-updates. The tricky part was that the auto update probably was for a different region as I was in Europe when the brick happened, but I live in Singapore.
Have tried to flash the firmware several times using Odin and even the PIT but all have been unsuccessful. I've been stuck a "Firmware upgrade encountered an issue....".
Have been able to get to the download screen but not the recovery mode.
Any pointers or is my phone rightly bricked?
I fixed my half brick using Android 4.0.4 ICS XXLAF2 stock firmware
My old stuff is still on my sd card, but not usable tho :s
Any tips? cant seem to restore with rom manager. It only fails
Help with encrypted at&t GS3
theonlyanil said:
It can be solved using Odin if you get the official and correct Stock ROM for your SGS3. And/Or you might have been using the Wrong PIT.
And finally, No idea about heimdall ;p
Hey Anil,
I have encrypted at&t samsung gs3 running CM10.1 nightly. For some reason I cannot undo the encryption. I want to use the method described on this link that you posted here to get rid of encryption.
I have downloaded official firmware from sammobile. But the .pit file available on that site is for internation version. I have at&t GS3 so i should be using the .PIT for at&t version. Could you please provide me .PIT for 16GB at&t Samsung galaxy s3, if you have one or you know the link? Ii appreciate your help.
please help me with this man.
-Ravi
Click to expand...
Click to collapse
Worked well
The method given by Anil worked fine.
And since my device was encrypted before, it asked me password after installing the firmware by Odin.
So for this I just entered recovery (Sam recovery) and did a factory reset, and the encryption was removed.:good:
Dude don't post ur serial or imie
Bananafische said:
Hi - I tried posting this in Development where I thought it should go but I haven't posted at all before so it won't let me.
I've gotten myself into a very messy (and probably stupid) situation with firmware with my I9300 - there's a very real chance I think that it is non-recoverable, but if anyone could give me some advice on what else to try I would be extremely grateful!
My problem:
Galaxy S3 I9300 16gb international won't boot - stuck at Device Name screen.
Won't boot into recovery
Will boot into download mode
Odin connects to device, but trying to flash stock ROM freezes at 'NAND Write Start!' or just FCs ("Odin has stopped working" reported by Windows
Heimdall won't recognise my device (does it even work with the s3? I don't know) so I can't print a PIT or anything
How I got here (over about 4 weeks):
Started with I9300 16gb international version (Grey import from Hong Kong to Australia, booted in French but let me change to English)
Gained root access through CWM touch kernel and Odin
Flashed AOKP Milestone 6 ROM
Used 'Secure Settings' (app) and 'Locale' (app) to set up a lockscreen PIN that enabled and disabled dynamically according to location rules (worked pretty well!)
Decided I wanted to encrypt my device
Clicked through all warnings, followed instructions to set PIN (didn't disable Secure Settings, the app that allowed the lockscreen changes outlined above)
Encryption successful, booted successfully using the PIN set
Lockscreen goes funny - 'quick PIN' option in AOKP (where you don't have to press OK after entering the PIN correctly) stops working
Any PIN at all at this point will unlock my device
Reboot to discover that my original encryption PIN has stopped working
Seriously, I tried it like 20 times including slight variations in case I mistyped, and other PINs that I use in case I misremembered
Rebooted into CWM to try to flash a new ROM
Can't access internal SD due to encryption
Use Galaxy S3 Toolkit to 'download and flash new stock rom, kernel using Odin'
Didn't know which firmware to download so i went with option 5 (GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2)
Odin connects sucessfully, flashes device
Device reboots into 'Trouble with firmware upgrade - connect to samsung kies to fix' (or whatever it says)
Download and install Kies (i had the USB drivers for the phone installed previously)
Kies won't recognise my phone on any level for emergency recovery
Decide that the internal SD card encryption is causing the problems, and that maybe I need to repartition
Don't notice all the warnings about repartitioning
Download PIT files for I9300 from somewhere
Try reflashing ROM using one of these PITs (I didn't know any better so I just used GT-I9300_mx_20120329.pit, which in retrospect is probably for a device with different internal storage size)
Phone stopped giving me 'Firmware update problem' screen and started going to the 'GT I9300' booting screen, but never got past that point
Repeat ad infinitum - I've tried flashing several different stock ROMs, using several PITs and am now at the point mentioned above.
Only other information I have really is that on the back cover behind the battery it says 'Model GT-I9300' and 'SSN-I9300GSMH' if those are important.
Other forums seem to indicate that I have a NAND read/write issue, but trying to flash a stock kernel (which was the advice given) results in... 'NAND write start!' freeze :\
Like I said, I have no idea if this is recoverable in any way at this point, but if anyone has any ideas I'd love to hear them!
Thanks
Click to expand...
Click to collapse
For ur own safety mate
Flashed Xperia's miui rom on S3-i9300
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
xcanpolatx said:
I have flashed Xperia's miui rom on S3-i9300, stack on boot what can i do? I did everything on the video.
Click to expand...
Click to collapse
Before you pay for a repair you can try flashing stock rom via Odin .
hi, my friend has a galaxy s2 i9100 on stock unrooted gingerbread, it crashes each time when turning on wi-fi,
i wanted to try to upgrade the the rom to see if the problem persist but unfortunately the kies encounters some error when upgrading the s2..
so i told my friend to try using odin, but odin also encountered an error (not sure what kind, im not with my friend when he tried)
do i need to match kernel to successfully flash the stock rom?
kies updated? closed all kies applications before flashing with odin? tried older odin versions? newer versions? tried all usb ports? another pc? a laptop? tried flashing siyah kernel?
Sent from the little guy
Without knowing the exact details of what's going wrong I.E exactly what your friend is flashing, what Odin says when it fails, what version Odin, etc, etc it's going to be nigh on impossible to provide any meaningful help.
At a guess, I'd say your friend is probably using Odin 3 (again, I'm guessing here because you've provided sod all info). Try flashing with an earlier version of Odin (Google search) & also check Windoze Task Manager & make sure Kies/it's processes aren't running when you're trying to use Odin. If they are, kill those processes.
MistahBungle said:
Without knowing the exact details of what's going wrong I.E exactly what your friend is flashing, what Odin says when it fails, what version Odin, etc, etc it's going to be nigh on impossible to provide any meaningful help.
At a guess, I'd say your friend is probably using Odin 3 (again, I'm guessing here because you've provided sod all info). Try flashing with an earlier version of Odin (Google search) & also check Windoze Task Manager & make sure Kies/it's processes aren't running when you're trying to use Odin. If they are, kill those processes.
Click to expand...
Click to collapse
why yes.. he is using odin v3+, i actualy recommended it becuase thats the version i used to flash my S3 over and over again, tnx for the help,
will definitely try a lower version of odin , will post what happens,
tnx alot
OK, so i have no idea where i went wrong but here we go.
I was flashing my phone (i9100 for reference) with the latest Neatrom ROM. seen here http://forum.xda-developers.com/showthread.php?t=1569686
from a stock samsung firmware on my international galaxy s2. so its not branded or anything. ( with virgin moblie canada if that matters... ) anyway booted into recovery. ( after putting the .zip file onto the phone ) and updated in the stock recovery to the Neatrom. THen i wiped dalivk and the normal cache. and rebooted.
i got the samsung logo and yellow triange..
tried factory reset
same thing.
(at which point i forgot to back up the phone like an idoit)
tried to use triangle away. ( got confused and gave up, never really even tried because it was a .apk and i didnt know how to launch it from a phone stuck on boot)
tried ODIN, by flashing the base samsung stock rom for virginmoblie canada phones.
and this is where i really got confused. the phone says that it needs to be connected to kies. so i installed kies ( because i never used before ) and kies wouldnt recognize the phone. ( also at this point the phone wouldnt go into recovery mode at all so i was really freaking out )
i then flashed siyah 6.0b5.tar on ODIN to the phone and thank God it flashed and the phone now went into recovery mode and i tried flashing neatrom agian and i was back to the start ( samsung boot logo with yellow triangle )
( i then flashed the stock rom and went back to the whole " please connect phone to kies, and the computer wont recognize it )
now i dont know what to do. my first idea that comes to mind is to reflash siyah kernel, after that im at a loss.
Any Help would be amazing
You need to successfully go back to stock & get a 'clean slate'. Then you can flash whatever custom rom//kernel you want again from there.
You've also gotten yourself seriously confused re: Kies & flashing with Odin. It's the opposite; you don't want Kies or any of its processes running (check & kill them in Windoze Task Manager if they are) because it messes with Odin. The reason Kies gets mentioned re: Odin flashes is because in order to use Odin you need to have drivers installed on the PC, and for many people the easiest way to do this is to simply install Kies.
I very much recommend to do an advanced search of Hopper8's threads & find his 'Odin won't flash' thread. I'd be very surprised if you can't end up successfully flashing the phone using the info in that thread.
MistahBungle said:
You need to successfully go back to stock & get a 'clean slate'. Then you can flash whatever custom rom//kernel you want again from there.
You've also gotten yourself seriously confused re: Kies & flashing with Odin. It's the opposite; you don't want Kies or any of its processes running (check & kill them in Windoze Task Manager if they are) because it messes with Odin. The reason Kies gets mentioned re: Odin flashes is because in order to use Odin you need to have drivers installed on the PC, and for many people the easiest way to do this is to simply install Kies.
I very much recommend to do an advanced search of Hopper8's threads & find his 'Odin won't flash' thread. I'd be very surprised if you can't end up successfully flashing the phone using the info in that thread.
Click to expand...
Click to collapse
Will try in a couple days ( i dont have my phone right now forgot it at home and im currently moving )
will post results
so go back to stock and get a clean slate should i reflash the siyah kernel through odin and flash a stock samsung rom?
just making sure here
Why would you 'reflash the siyah kernel through odin and flash a stock samsung rom?' if you've already just flashed a stock rom through Odin ? Take some deep breaths, lose the panic & re-read my last post slowly.
I got myself an AT&T branded S2 (i777). I used Samsung Kies to update to the latest firmware and something happened while doing so. I turn on the phone now and it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Recovery in Kies doesn't work.
I can get into download mode. Although I can't seem to get Odin to be successfully done, always fails.
Is there any solutions to fix my problem?
I have searched and found fixes for the international version, but that does me no good as mine is the SGH-I777. I just want to be able to have a working phone again.
I'm pretty sure we can get your phone back to working.
A more detailed description of your inability to flash with Odin would be helpful.
What were you trying to flash?
Were you able to get Odin to recognize the phone?
What were the error messages in Odin?
After you answer, I'll give you some things to try.
That would be awesome.
- Tried using I777UCKH7-CL503881-Full it gets to sbl.bin and then fails.
- Tried using Odin v1.85 with a stock i777 tar file. Sticks at factoryfs.img and then fails.
- Odin does recognize the phone.
The majority of issues with failed flashes have to do with the connection between the computer and the phone. The standard advice is, use another cable, use another USB port on the computer, or even use another computer. However, lets skip that step for now, and assume that the connection is good.
It's possible that there is an issue with nand read/write memory corruption. Let's see what happens if we clear nand r/w memory. I assume that you know how to use Odin correctly, but if you want additional instructions, I can post some.
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Link to the download repository is in my sig.
---------- Post added at 09:04 PM ---------- Previous post was at 08:57 PM ----------
The latest stock for this phone is I777UCMD8, which you can also get in the Download Repository. I would suggest you flash that after you get the phone back to working. Or, if you want to customize, there are good versions of custom firmware available in the forums.
I try to check in to the forums every couple of days, at least. It was just serendipity that I came into the forum 10 minutes after you posted. I'll try to remember to keep an eye on this thread more often, but sometimes I get a littly busy, so if I'm mia, just be patient.
Re-tried Siyah with a different cable and used back usb ports instead. Was successful with Siyah.
I don't want to mess the phone up anymore than needed, which exact one should I flash?
fluttershys said:
Re-tried Siyah with a different cable and used back usb ports instead. Was successful with Siyah.
I don't want to mess the phone up anymore than needed, which exact one should I flash?
Click to expand...
Click to collapse
Okay. Maybe your issue was only a connection issue. But I would suggest that you complete the sequence above exactly as written. As it says, instructions are specific; do them in order, and don't skip.
If the issue is nand r/w corruption, this should fix it. If that was not the issue, this will not do any harm. The firmware used is the oldest original firmware for the I777, and is seriously out of date. But it is known to fix the specific issue of nand r/w corruption.
Once you have the phone working normally, ie. booting into system without issue, then you should probably flash the latest stock firmware as I suggested earlier, or the custom firmware of your choice.
Thank you for all the help. I was actually able to use Kies and re-do the firmware that way. I have done the framaroot root.
Is there a ROM and Kernel that you would suggest using for the I777?
You need to decide whether you want firmware that is Samsung touchwiz based, or AOSP based.
If you want touchwiz, you should look at cooked or SHOstock3. No one is doing active development right now, but these two are stable and each is good in its own way.
If you want AOSP, I can't recommend anything since I haven't flashed them, but would suggest you read the development forum and look at the threads for firmware that have been actively posted in the past few months.
The latest touchwiz is Jelly Bean, but with AOSP you can get Kit Kat, or even Lollipop.