To start with: Odin stuck's at flashing.
Details:
Model: Samsung Galaxy S 2 I9100Т, almost 2 years have past since it was purchased.
History of ROMs used: Almost after the purchase it was flashed with the latest nightly Cyanogenmod 9+ something that is 4.0.1 Android.
But the ROM was for normal SGSII, not T, although it worked good for something about a year. It was flashed with stable Cyanogen 9.1, also not for the T. With that ROM it worked another 7-8 months and suddenly got a problem with "Apps not responding at all". So, first it was factory reseted via CWM recovery, and after that, i was asked to get a new OS for it. So i flashed nightly Cyanogen 10.1xx. All ROMs, that were used with this device, were downloaded from the Cyanogenmod "official site".
Case History: After a month of doing well with 10.1 nightly, during a downloading or even installation process of a casual, but a 3D game, with a size of 20+ megaz, it suddenly got stuck and stoped responding to any input. It was rebooted by taking out the battery, w8ng for a few mins, and putting it back. After that it started to get stuck, right on the loading screen, repeatedly. I tried wiping cache via recovery: it was "doing something" for 5 mins and then saying: "Kernal Panic". Then i tried factory reset option, and the result was the same. Also, installing a new ROM via install zip recovery feature, that ended with the same message, also after a long w8ng time.
Not so successful Reanimation history: While trying to flash official service 1 file NEE (Nordic Contries) firmware 4.0.4 with Odin 1.85, it got stuck almost right at the start, while it was trying to flash a "cache" part, the process status bar havent appeared on the device even after 20 minutes of wating time. So i decided that it should be disconnected from the PC for good. That led to a standart soft brick, with a picture: "mobile - ! - PC " and a message, asking to flash something, that actually works with Kies. Download mode is still availible but recovery isn't anymore.
I tried flashing with Odin 1.85 and 3.04, and even 3.07. I tried flashing quite an amount of offcial firmwares: 2.3.3 и 4.0.3 и 4.0.4. и 4.1.2, both 1 file and 3 file versions. All the same: it kept getting stuck almost at the start, with a message or process, depending on a firmware version, but always same for the same ROM, and as i said before the process bar havent appeared on a phone even for a moment during all those attempts.
Notice: The PC, that was used to Odin-flash this device, a month before was able to flash another SGSII and did it perfectly.
Thanks in advance to everyone, who may help me in this "case", and sorry for not so good english.
Chellout said:
To start with: Odin stucks on flashing on this device.
Details:
Model: Samsung Galaxy S 2 I9100Т, almost 2 years past since it was purchased.
History of ROMs used: Almost after the purchase it was flashed with the latest nighlty Cyanogenmod 9+ something that is 4.0.1 Android.
But the ROM was for normal SGSII not T, although it was working good for something around a year. It was flashed stable Cyanogen 9.1 then, also not for the T, With this it worked another 7-8 months and suddenly got a problem with Apps not responding at all. So first it was factory reseted via CWM recovery, and after i was asked to get a new OS for it. So i flashed nighly Cyanogen 10.1xx. All ROMs that were used with this device were downloaded from the Cyanogenmod "official site".
Case History: After a month of going well with 10.1 nighly, during a downloading or even installation process of a casual but a 3D game with a size of 20+ megaz, it suddenly got stuck and stop responding to any input. It was rebooted by taking out the battery w8 for a few mins and putting it back. After that it started to get stuck right on the loading screen repeatedly. I tried wiping cache via recovery it was "doing something" for 5 mins and then saying: Kernal Panic. Then i tried factory reset option and the result was the same. Also installing a new ROM via install zip recovery feature ended with the same message after a long w8ng time.
Not so successful Reanimation history: While trying to flash official service 1 file NEE (Nordic Contries) firmware 4.0.4 with Odin 1.85, NEE, it got almost right at the start while it tryied to flash a "cache" part, the process status bar havent even appear on the device even after 20 minutes of w8ng time. So i decided that it should be disconnetcted from the PC for good. That led to a standart soft brick with a picture : "mobile - ! - PC " and a message asking to flash something that actually works with Kies. Download mode is still availible but recovery isn't anymore.
I tried flashing with Odin 1.85 and 3.04 and even 3.07. I tried flashing quite an ammount of offcial firmwares: 2.3.3 и 4.0.3 и 4.0.4. и 4.1.2, both 1 file and 3 file versions, it was all almost the same: it got stuck almost at the start with a message or process depending on a firmwave version but always same for the same ROMs, and as i said before the process bar havent appeared on a phone even for a moment during all those attempts.
Notice: The PC that was used to Odin-flash this device, a moth before it was able to flash another SGSII and done it perfectly.
Thanks in advance to everyone, who may help me in this "case", and sorry for not so good english.
Click to expand...
Click to collapse
Siyah? No siyah? How come no siyah?
Flash siyah.
gastonw said:
Siyah? No siyah? How come no siyah?
Flash siyah.
Click to expand...
Click to collapse
I'll gladly do it, once i'm able to get something to work on this device. Thanks.
Chellout said:
I'll gladly do it, once i'm able to get something to work on this device. Thanks.
Click to expand...
Click to collapse
Forced download screen? Flash it with odin.
gastonw said:
Forced download screen? Flash it with odin.
Click to expand...
Click to collapse
Apparently, i guess y havent read the whole post.
just uninstall the drivers , restart pc and then reinstall the drivers on the pc and c if that works :/ or this http://forum.xda-developers.com/showthread.php?t=1457458
It sounds to me that you have a hardware failure and there is nothing you can do. If your rom was somehow messed up, then your recovery should have been fine. Try returning it to stock as much as possible and send the device to samsung. Try to atleast reset your download counter.
Chellout said:
Apparently, i guess y havent read the whole post.
Click to expand...
Click to collapse
Kid, noticed tha pc logo with the exclamation sign in the middle?
Thats forced download.
Sent from the little guy
gastonw said:
Kid, noticed tha pc logo with the exclamation sign in the middle?
Thats forced download.
Sent from the little guy
Click to expand...
Click to collapse
Yes, i can easlly enter Download mode aka Odin mode, from this with 3 fingers method. But as i mentioned in the first post, Odin doesn't want to flash anything, it stops right at the start.
If you can provide me a link to the cure, ill be greateful.
There's no magic link.
How many odin versions have you tried?
Kies applications closed?
Sent from the little guy
gastonw said:
There's no magic link.
How many odin versions have you tried?
Kies applications closed?
Sent from the little guy
Click to expand...
Click to collapse
1.85, 3.04. 3.07. and 4.42 none of them were able to get the process bar moving.
Kies uninstalled even, tho i have the drivers.
Install kies, then close it all up.
Post the log to see where odin fails / stops
Sent from the little guy
gastonw said:
Install kies, then close it all up.
Post the log to see where odin fails / stops
Sent from the little guy
Click to expand...
Click to collapse
Done with Kies. What exactly you think i should try to flash with Odin to provide you the output?
And btw, the last working OS was custom JB by cyanogenmod.
Chellout said:
Done with Kies. What exactly you think i should try to flash with Odin to provide you the output?
And btw, the last working OS was custom JB by cyanogenmod.
Click to expand...
Click to collapse
Yes, remember cm from OP.
You could flash LSJ (google "jelly bean test firmware s2 sammobile") so you can get the odin fail log up on the screen.
Flash only csc, code and modem.
Sent from the little guy
gastonw said:
Yes, remember cm from OP.
You could flash LSJ (google "jelly bean test firmware s2 sammobile") so you can get the odin fail log up on the screen.
Flash only csc, code and modem.
Sent from the little guy
Click to expand...
Click to collapse
Okey, so im trying to flash this http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
with the provided 3.04 Odin.
Gona post the resut soon.
Chellout said:
Okey, so im trying to flash this http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
with the provided 3.04 Odin.
Gona post the resut soon.
Click to expand...
Click to collapse
Try odin 1.85 also, it's know to work better sometimes.
Mistaken.
Chellout said:
Mistaken.
Click to expand...
Click to collapse
What is that you are flashing there?
EDIT: Lol
gastonw said:
What is that you are flashing there?
EDIT: Lol
Click to expand...
Click to collapse
Now i flashed it, though result is the same, sadly almost same as it was during all my previous tries:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> data.img
And here it is... for anothe 10 minutes, roughly
And the screenshot here:
Chellout said:
Now i flashed it, though result is the same, sadly almost same as it was during all my previous tries:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> data.img
And here it is... for anothe 10 minutes, roughly
And the screenshot here:
Click to expand...
Click to collapse
Ok, so it get stucked there in all usb ports?
Sure looks like nand corruption.
Related
Hi everyone, I'm in a bit of trouble and I am really hoping that someone can help me out.
Yesterday I was flashing some rom or kernel or something and for some reason decided to try to repartition(my stupid mistake), but Odin stayed on Do Not Turn Off Target for a few hours so I thought I had no other choice but too restart the process, so I unplugged it. Well since then I get the phone-!-Computer, but I am still able to get to the download screen.
The problem is this:
<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> Complete(Write) operation failed.<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What I have tried so far:
1) flashing stock, and other versions-same result
2) using different computers, different OS ( 7 and XP )
3) Odin v1 and v1.3
4) changing the port number
5) trying to repartition again, always hangs for hours at Do Not Turn Off Target
6) I have tried many, many times
I have found others having similar issues but most were able to fix by reflashing to stock, didnt work for me.
I would greatly appreciate any help, thank you
did you install the Samsung drivers on your computer?
First off WRONG forums, more than likely it's you don't have the drovers installed correctly or it's not recognizing the phone correctly in odin
Sent from my SGH-T959 using XDA App
Yes, I forgot to mention that but I do have the drivers installed. Over the past few days all has worked pretty well, things just went bad after i checked the repartition box and Odin hung.
stefan.buddle said:
First off WRONG forums, more than likely it's you don't have the drovers installed correctly or it's not recognizing the phone correctly in odin
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Sorry about that, I am pretty freaked out over this, didnt think to post elsewhere. If moderators can move to appropriate forum, thank you.
I am pretty sure that the drivers are correct and working, I have gone from stock to JI6 and back to stock in the last week with Odin. Also I was able to get adb to work before this happened. Thanks for the input guys.
marin 8703 said:
Sorry about that, I am pretty freaked out over this, didnt think to post elsewhere. If moderators can move to appropriate forum, thank you.
I am pretty sure that the drivers are correct and working, I have gone from stock to JI6 and back to stock in the last week with Odin. Also I was able to get adb to work before this happened. Thanks for the input guys.
Click to expand...
Click to collapse
Well repartition isn't anything to be scared of in odin. I would recommend downloading eugene373s froyo that doesnt brick, flash that via odin with repartition checked, then flash back to stock with repartition unchecked. This fixes voodoo soft bricks among other types of bricks. If using windows vista or windows 7 to open odin right click on it and run as administrator. I've heard it sometimes workes without that step, but I never got it to work without doing that.
Edit: also try redownloading the pit file, sometimes if it gets corrupted it can cause problems.
Sent from my SGH-T959 using XDA App
wildklymr said:
Well repartition isn't anything to be scared of in odin. I would recommend downloading eugene373s froyo that doesnt brick, flash that via odin with repartition checked, then flash back to stock with repartition unchecked. This fixes voodoo soft bricks among other types of bricks. If using windows vista or windows 7 to open odin right click on it and run as administrator. I've heard it sometimes workes without that step, but I never got it to work without doing that.
Edit: also try redownloading the pit file, sometimes if it gets corrupted it can cause problems.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I will try this right now...
Tried this and get the same result. While doing this with repartition checked, Odin hangs again, also tried with repartition unchecked and receive the same result as in first post.
I also tried flashing the stock kernel and it gives pretty much the same result except it fails after zImage instead of cache.rfs. It looks like it just cant write anything. What could be wrong?
<ID:0/002> Added!!
<ID:0/002> Odin v.3 engine (ID:2)..
<ID:0/002> File analysis..
<ID:0/002> SetupConnection..
<ID:0/002> Initialzation..
<ID:0/002> Get PIT for mapping..
<ID:0/002> Firmware update start..
<ID:0/002> zImage
<ID:0/002> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
marin 8703 said:
I will try this right now...
Tried this and get the same result. While doing this with repartition checked, Odin hangs again, also tried with repartition unchecked and receive the same result as in first post.
I also tried flashing the stock kernel and it gives pretty much the same result except it fails after zImage instead of cache.rfs. It looks like it just cant write anything. What could be wrong?
Click to expand...
Click to collapse
Not sure, as far as I can tell you're doing it right. Maybe an actual malfunction. With the ota bricking a lot of phones of non modders, tmobile wont suspect one more person calling in for an exchange.
Edit: did you redownload the pit file?
Sent from my SGH-T959 using XDA App
wildklymr said:
Not sure, as far as I can tell you're doing it right. Maybe an actual malfunction. With the ota bricking a lot of phones of non modders, tmobile wont suspect one more person calling in for an exchange.
Edit: did you redownload the pit file?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yea i re-downloaded everything, but still no luck. I guess its not gonna happen
If nothing works out in the next day or so, I'm going to give t-mobile a try.
Thanks for all the help, if anyone has any other suggestions I'm still willing to try.
Some great news. I'm back in business with my vibrant. The issue seems to have something to do with odin, because after several tries WITHOUT closing odin it worked. Until now I would restart odin because I thought that might help but the opposite worked better.
With that and the advise that wildklymr provided I was finally able to flash back to stock.
Thank you very much for the help, really appreciate it.
Sent from my SGH-T959 using XDA App
marin 8703 said:
Some great news. I'm back in business with my vibrant. The issue seems to have something to do with odin, because after several tries WITHOUT closing odin it worked. Until now I would restart odin because I thought that might help but the opposite worked better.
With that and the advise that wildklymr provided I was finally able to flash back to stock.
Thank you very much for the help, really appreciate it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I just ran into the same problem as you tonight. I tried what you did with not closing odin and it worked for me too.
how many tries of not closing odin til it worked?
im actually experiencing this now on my Galaxy TAB.
lol .. multiple tries .. changing the USB ports .. and reinstalling drivers worked for me .. phew .-.
Thanks guys, had the same problem.
Had to retry without restarting ODIN and it worked.
Took 3 tries, was in a bit of a crisis as I've never seen the phone-!-Computer before
The opposite worked for me. Had to restart Odin.
I too had the same problem. Had to hit the "Start" just one more time (without restarting ODIN) to take care of it.
same for me... about three times with changing ports... nightmare ;/
Good News - Found Fix!
Keep Odin open and change USB ports, remount the PDA & flash. Hope this helped, worked for me
marin 8703 said:
Hi everyone, I'm in a bit of trouble and I am really hoping that someone can help me out.
Yesterday I was flashing some rom or kernel or something and for some reason decided to try to repartition(my stupid mistake), but Odin stayed on Do Not Turn Off Target for a few hours so I thought I had no other choice but too restart the process, so I unplugged it. Well since then I get the phone-!-Computer, but I am still able to get to the download screen.
The problem is this:
What I have tried so far:
1) flashing stock, and other versions-same result
2) using different computers, different OS ( 7 and XP )
3) Odin v1 and v1.3
4) changing the port number
5) trying to repartition again, always hangs for hours at Do Not Turn Off Target
6) I have tried many, many times
I have found others having similar issues but most were able to fix by reflashing to stock, didnt work for me.
I would greatly appreciate any help, thank you
Click to expand...
Click to collapse
Hello Buddy if you are under Windows 7 or 8 try to LUNCH Odin with Administrator
hi guys
i also have this problem
but my problem is a little different
im trying to flash stock rom 5.1.1 for my galaxy note4 (n910c) but i see the same problem as you had
but i can flash all roms that i have downloaded them before except this rom
so seems like the problem appears with some certain roms
so you have to download another rom and flash it regularly
but i didnt realize that is the rom really corrupted?
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
niches said:
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
Click to expand...
Click to collapse
Return under warranty .
jje
JJEgan said:
Return under warranty .
jje
Click to expand...
Click to collapse
yeah, problem is I bought it from amazon.de so I have to send it then via Post :S
tumult said:
full firmware flash with pit, bootloader, tz, etc..
hooe the link still works, if not i can make mirror tomorrow
also check in Odias thread in original android development if pit for 16 & 32 is same, but as far as i remember it is.
ps. i have flashed this firmware (without pit, but it is safe to download , no viruses, etc).
hope it helps
Click to expand...
Click to collapse
Thanks, I'll try it when I arrive home from celebrating the 253rd birtday of Mr. Guiness
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
as i9000 said:
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
edit: i was wrong, all partitions are there.
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
tumult said:
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
Click to expand...
Click to collapse
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
as i9000 said:
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
Click to expand...
Click to collapse
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
tumult said:
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
Click to expand...
Click to collapse
should not be deleted link, and the Russian people attend the xda forum ...
tumult said:
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
Click to expand...
Click to collapse
this is all great, but I think that does not work, I have met with this diagnosis: "there is no pit partition"
INTERNAL MMC IS DEAD... ((((
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<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)
TinyGrasshopper said:
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<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)
Click to expand...
Click to collapse
Hey all, I have exactly the same error message. Running cm10 and my phone just froze, after re-boot i'm stuck on boot screen, no recovery and can only enter download mode....HELP!!!!
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
PjotrFias said:
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
Click to expand...
Click to collapse
thanks for the reply, i tried it but to no avail :crying:
Where did it stop? The first part?
PjotrFias said:
Where did it stop? The first part?
Click to expand...
Click to collapse
yeah i got the no pit message, tried flashing the pit file but won't do it...
I've just received this error on my phone too, Has there been any progress on solutions to this?
Another problem is that I can get into download mode and my system status is "Custom", How will this effect a return to manufacturer?
alot of replies with this errors lately...u guys used any custom FW ?
Hi
Yesterday i rooted my Samsung Galaxy S2 i9100m VIA The zergrush exploit.
I Tried to flash CWM Via Odin and it did not work!
My phone will not access recovery and when turned on normally says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I have tried flashing the bootloader, kernel, CSC, modem, and firmware several times but they always fail!
I tried to follow this guide here and it also did not work!
I can not think of what else to do so i have posted this thread here!
Thanks
*EDIT*
This is what originally ****ed me up: http://galaxys2root.com/galaxy-s2-r...ckworkmod-recovery-on-rooted-galaxy-s2-i9100/
if you read the comments everyone is having the same issue
*EDIT*
- What is the error you were getting in Odin=I have successfully flashed a pit file and when trying to flash my firmware it comes up with 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> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So it is failing at NAND Write Start!!
- Did you try to flash other recovery's? If yes, then which one= No but i am now
- Do you still have download mode= Yes
- Did you flash .pit files or re-partitoned= Yes i flashed the correct pit file and it succeeded
- What firmware were you on= I9100MKG2
- Did you reinstall the drivers= Several Times
- Tried different usb port / pc= Yes
- Did you try different cables= Yes
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
gastonw said:
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
Click to expand...
Click to collapse
Yes i have!
Flash custom kernel so you can get to recovery then.
And if you tried that too keep on flashing.
Hold on a sec, odin passes or fails?
Sent from the little guy
gastonw said:
Flash custom kernel so you can get to recovery then.
And if you tried that too keep on flashing.
Hold on a sec, odin passes or fails?
Sent from the little guy
Click to expand...
Click to collapse
It fails
Jenham said:
It fails
Click to expand...
Click to collapse
it fails
You gotta keep on trying. Trial & error.
Sent from the little guy
gastonw said:
So I guess you've flashed a stock I9100M ROM via odin and failed too, right?
Sent from the little guy
Click to expand...
Click to collapse
Updated
?
Got it working again?
Sent from the little guy
Jenham said:
Updated
Click to expand...
Click to collapse
Huh?
Sent from my digital submersible hovercraft.
You need to start giving more details if you want help...
- What is the error you were getting in Odin?
- Did you try to flash other recovery's? If yes, then which one?
- Do you still have download mode?
- Did you flash .pit files or re-partitoned?
- What firmware were you on?
- Did you reinstall the drivers?
- Tried different usb port / pc?
- Did you try different cables?
If you want help, I suggest you start giving us all the info that you can give us instead of saying "they always fail".
He's mute.
Sent from the little guy
Lennyz1988 said:
You need to start giving more details if you want help...
- What is the error you were getting in Odin?
- Did you try to flash other recovery's? If yes, then which one?
- Do you still have download mode?
- Did you flash .pit files or re-partitoned?
- What firmware were you on?
- Did you reinstall the drivers?
- Tried different usb port / pc?
- Did you try different cables?
If you want help, I suggest you start giving us all the info that you can give us instead of saying "they always fail".
Click to expand...
Click to collapse
Sorry about that and i have updated my thread!
Oh boy, did I just read that you used a .pit file and that the flashing failed? You do know that the flashing needs to succeed when you flash a .pit?
Did you use a .pit the first time when the flashing failed?
http://forum.xda-developers.com/attachment.php?attachmentid=1750999&stc=1&d=1361525591
Really should stay well away from .pit files man.... Reads like jtag or paperweight time.
Amen.
Sent from the little guy
gaosphappy said:
http://forum.xda-developers.com/attachment.php?attachmentid=1750999&stc=1&d=1361525591
Really should stay well away from .pit files man.... Reads like jtag or paperweight time.
Click to expand...
Click to collapse
Lol the pit succeeded
Take a long breath, and when I say long I mean LONG.
Sent from the little guy
Hi I'm in the exact same boat, My sgs2 wont reboot and wont go into recovery. Everytime I flash with odin I get failed. What can I do ? I can't even find the pit file to flash that. I'm getting really worried. Please help
sawdoctor said:
Hi I'm in the exact same boat, My sgs2 wont reboot and wont go into recovery. Everytime I flash with odin I get failed. What can I do ? I can't even find the pit file to flash that. I'm getting really worried. Please help
Click to expand...
Click to collapse
Check the phistachio thread.
Sent from the little guy
Hi,
I've got this problem with a friends(girl) phone.
Her phone was stuck at the firmware upgrade screen(the one with firmware upgrade encountered an issue). So she searched the internet for a solution and did some things with kies and odin. But nothing worked so i offered to help her.
So i searched and found this article. i followed all the instructions and downloaded 3 different versions of odin V3.07, V1.3 and V1.85.
Specifications of the phone:
samsung Galaxy S II GT-I9100 16GB
what i've tried so far:
i followed the instructions from te link above and tried it with the following roms
-I9100GXXLB1_I9100GATOKL1_ATO
-I9100XWLP9_I9100KPNLP1_KPN
-I9100XXLSJ_I9100OXXLS1_OXX
i also tried the gingerbread and the ICS version
i also tried the pit file. but nothing works, the progress get stuck like in this example
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help me with this problem? I also have a JTAG programmer but don't know how or what to do with it.
Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Look for hopper8's thread.
And stop flashing pit files.
Sent from the little guy
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Basseytje said:
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Click to expand...
Click to collapse
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
when u go to download mode, does it show your model number??
Hopper8 said:
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
Click to expand...
Click to collapse
I've already tried that one but odin is stuck at data.img.
tornado92 said:
when u go to download mode, does it show your model number??
Click to expand...
Click to collapse
Yes it shows the product name.
Basseytje said:
I've already tried that one but odin is stuck at data.img.
Yes it shows the product name.
Click to expand...
Click to collapse
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
tornado92 said:
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
Click to expand...
Click to collapse
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Basseytje said:
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Click to expand...
Click to collapse
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
tornado92 said:
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
Click to expand...
Click to collapse
kies won't recognize the phone. the only 3 screens i can access are showed in the pics below. i've got 2 stock roms which don't work. after i tried kies, i immediately uninstalled it and left the drivers on the pc.
i40.tinypic.com/29gkdi1.jpg
i40.tinypic.com/qsnluc.jpg
i41.tinypic.com/2aep3yx.jpg
can't post any files yet.
I hope there is still someone who can help me...
odin is still stuck on data.img
If you say you've 'tried everything' (which everyone always says), then it's a service centre job. What else do you want anyone here to say ? No miracle fixes. If it were me I'd keep trying, it's almost always something really simple/small/obvious that's causing the flash not to work, and as we're not there looking over your shoulder at what you're doing, it's going to be almost impossible for anyone to say what that is (you have 'tried everything' after all).
is there a way to fix this with jtag?
Basseytje said:
is there a way to fix this with jtag?
Click to expand...
Click to collapse
Maybe. No one can say for sure mate. If you motherboard is really borked, it would have to be replaced nevertheless.
Remember that Jtagging leaves marks on your device, so you can kiss goodbye any warranty u might have.
"To err is human, to forgive is divine."
Sent from my SGS II
hey.. i had this problem too.. the only solution that i had is to use the galaxy note pit file and a stock rom for i9100 ... then the phone went back to normal ..but the memory went from 16 tb to 11.5 gb .. it was the only thing that made my phone work again..
i installed pit from galaxy note ..with and original stock firmware 4.1,2 then after install I did a factory reset via stock cwm and a clear cache ..and it worked.. a few bootloops and it went on:|
alexandru.j91 said:
hey.. i had this problem too..
Click to expand...
Click to collapse
You got so ridiculously lucky that I can't comprehend that it worked. Please don't advise others to do the same, I'd say what you did is normally a recipe for a hard brick. Don't flash files for other phones, let alone a pit file for another phone. Yes I know the note has the same hardware as i9100 but you know what? It's not an i9100.
Edit: Look at what you posted in your other thread:
alexandru.j91 said:
I hardbricked my phone about 3 months ago with the original firmware from orange 4.0.4 and I resolved the problem by putting samsung note PIT file ..but I don't have acces to all the memory on my phone ..I have almosst 12 gb from 16.. and my phone is getting wired ..and it is shutting off randomly since then .and to get it on again i have to remove the battery ..
Does anybody know how to get all my memory back for my phone? tx
Click to expand...
Click to collapse
I'd say that's a reason not to flash files from another phone.
i was just telling him that i had the same problem..not to do the same thing..because of the problem that I have got! i have told in my other post whathappened to my phone! and i know that my problem can be solved by rewriting the memorybut i don't know how!..
---------- Post added at 06:04 AM ---------- Previous post was at 05:05 AM ----------
what I did.. i did because of some threads on xda ..so I am not crazy ..I just told him what I have did.. I haven't advised him to do that ..because of the problem that i had .. and when I wrote what I have did to make my phone worked .. i hace told the fact that it shrinked my memory from my phone..
maybe i'm getting a little progress. when i try to flash a new bootloader. i see a progress bar on the phone. but odin is halfway stuck at sbl.bin
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Sbl.bin
everywhere i read, people are saying use different cables. i already tried the samsung s2 cable, a htc desire cable, 3 deal extreme cables and an other htc(dont remember the model) cable. but i'm getting the same problems. stuck at zimage or something else...
anyone?
Hello all,
I want to preface everything that while I know a bit about rooting and messing with the stock status of android phones, I'm still generally a newbie at this.
Last night I started experiencing problems with my phone. I was using it normally until it ran out of battery while in a call, but I figured this happened in the past so it shouldn't be a problem. I plugged it in, however it wouldn't boot up. The CM11.2 loading screen just wouldn't stop spinning. Booting into recovery and download mode was working fine, but I couldn't get into the OS. Since I wanted for a long time to upgrade my Jellybean to Lollipop (and found this thread http://forum.xda-developers.com/gal.../rom-cyanogenmod-12-1-nightly-builds-t3147661 just last night), I decided it's time.
I boot into recovery and try and backup my data, but as soon as I click, the device freezes. Fast forward 5 attempts later with 3 different SD cards, it would still do the same thing. Already annoyed, I decide just to factory reset/wipe data, in order to flash the new Nightly and Gapps. As soon as I click, same thing happens, the CWM freezes and I have to manually reboot.
I figured the CWM is corrupt and I started searching on forums what to do. Tried flashing a new CWM with Odin (specifically this) but now I can't boot into recovery anymore, only download mode. I'm scared of doing more on my own. The current state of the phone is that it stays frozen at the "Samsung Galaxy S2" screen, the one with the yellow triangle w/ "!". Could you please help?
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
noppy22 said:
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
Click to expand...
Click to collapse
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
I tried getting a stock firmware from Sammobile, specifically firmwares/confirm/14909/I9100XWLSU_I9100OROLS5_ORO/. I tried flashing it, and this happened:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWMS2_I9100BULS3_I9100VDFLSF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ricksis said:
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
Click to expand...
Click to collapse
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Anyway get a stock rom for your region from
sammobile.com
or http://androidfirmwares.net/Home/sgs2
or http://www.tsar3000.com/Joomla/inde...alaxy-sii-firmware&catid=55:samsung&Itemid=82
noppy22 said:
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Click to expand...
Click to collapse
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Ricksis said:
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Click to expand...
Click to collapse
I'm not sure you can expect anything. It's just a common problem. See if you can get it fully charged and try the stock rom with odin again. Also check out this guide
As I said it seems like there is a hardware problem, the battery is just where I would start. Once you can rule that out you can look elsewhere
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
Click to expand...
Click to collapse
I tried with multiple stock roms, but they all fail in the same stage. I bought the phone carrier free, and its code is GT-I9100 (no extra letters afterwards like a lot of S2s have). I also found another solution, but it stopped after NAND WRITE start.
Hopper8 said:
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: or here. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Click to expand...
Click to collapse
I also found this http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
I've had a quick look at the thread you linked to, and from what I understand, the OP is providing a way to flash the firmware partition by partition......
In theory, this is a good solution, but unfortunately, I don't know enough about the firmware structure or about the odin flashing process to be able to meaningfully pass comment on that method.......My uninformed instinct tells me 'why not'......but my practical, logical side tells me 'caution'....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
Click to expand...
Click to collapse
In Odin 3.07, everything but PDA is greyed out for me. I donwloaded v1.85 and tried the 3 part thing: Odin freezes at NAND Write Start!!, and as for my phone, there is no blue progress bar appearing on the screen in the first place while i'm in download mode.
Just tried the pit file solution as well:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
Things to check for odin flashing.......
1) firewall disabled
2) antivirus disabled
2) all Kies processes killed (use task manager)
4) run Odin as administrator
5) only use main board USB sockets (pc/laptop side)
6) make sure Samsung drivers correctly installed.
7) windows 8 & 10 may not allow odin to operate correctly.
8) Use official Samsung usb lead.....no cheap s**te off eBay
9) try all usb ports on pc/laptop
10) try different cables
11) try different PC's/Laptops.......
12) do the whole procedure multiple times.....Odin flashing is a bit like playing the lottery......it may not work the first 9 or 19 times, but for some reason, on the 10 or 20th attempt, it does.......
The only thing that will 'win the day' is perseverance......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
There is (possibly) a plan B.......
Are you able to get into recovery?
If you are, you *could* try flashing PhilZ recovery which will root your phone.....then you can give flashing a custom rom a try.......
You possibly still could go that route even without recovery......by (maybe) Odin flashing a custom kernel .tar and then flashing a custom rom......
(I'm not talking about the latest CM12. ....but an older KK or JB based rom.....they're far more stable and complete than the LP based roms.....)
http://i.imgur.com/rVnFwJM.jpg
I had a busy week and only could try some solutions today. Unfortunately, I think they ended up with the hardbrick of my phone, as I am not able to turn it on anymore, not even in download mode.
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
Click to expand...
Click to collapse
I'm not sure, but I kinda fiddled enough with ODIN for just the battery to be the cause. Of course I am no expert, but I see no connection between the battery failing and all the other problems: cwm11.2 not wiping cache/dalvik or performing factory resets, the option to only boot in download mode later, etc. When I plug the phone to the USB port, nothing happens anymore.
Sooooo... RIP phone? ...
Ricksis said:
Sooooo... RIP phone? ...
Click to expand...
Click to collapse
If you are sure there's nothing else you can try........
But, even though it's an old device, it's still going to cost money to replace it....
You mentioned that odin failed to recognise it......
Another *possibly* would be the USB socket......
It would account for the lack of odin recognition *AND* a dead (uncharged) battery which could lead you to assume the whole phone is dead.
The port may have been ok at the start of your recovery attempts, but they do wear out (especially on older devices simply due to wear and tear) and by the last attempt it could have failed......
The part costs pocket change on ebay and is relatively easy to replace....I've done it myself......
Here's a guide I wrote on replacing the board......
http://forum.xda-developers.com/showthread.php?t=2335961
http://i.imgur.com/rVnFwJM.jpg