Hello guys!
First of all, I'd like to say Hi to everyone here, because it's my first post, even if i was seeking and reading forum earlier.
Okay, so from the beginning.
I got that phone from a girl who tried to unroot it and change FW. Now, the phone just boots, and stucks on the bootscreen, or goes to Download Mode, and:
1. I don't know what firmware it really is.
2. IMEI is still unknown, until tomorrow, i hope so.
3. I tried to flash everything, just EVERYTHING and:
- I can flash all kind of PIT files, hadn't tried with custom PIT's
- Also, I'm able to flash all kinds of bootloaders, but without any visible changes in phone
- I made my own JIG USB PLUG, but no matter how hard i tried, it didn't work (i'll try tomorrow with 301k, instead of 300k, but i think it's too small difference to work different)(+++ it didn't work even with older bootloader, even with two types of turning off the phone)
- Phone is recognized by system as Samsung Device, but after bootscreen stucking, it changes to an unknown device.
- Flashing kernel ends up with boot.bin and stucks
- Flashing other stuff ends up with NAND Write Start!! or zImage etc.
- I tried all versions of Odin.
I'm getting tired after 4 days, and nights of trying to rivive that screwsung (sry, i'm really mad )
So, again: What am I supposed to do? Any ideas?
Thanks in advance,
CU tomorrow!
celu said:
Hello guys!
First of all, I'd like to say Hi to everyone here, because it's my first post, even if i was seeking and reading forum earlier.
Okay, so from the beginning.
I got that phone from a girl who tried to unroot it and change FW. Now, the phone just boots, and stucks on the bootscreen, or goes to Download Mode, and:
1. I don't know what firmware it really is.
2. IMEI is still unknown, until tomorrow, i hope so.
3. I tried to flash everything, just EVERYTHING and:
- I can flash all kind of PIT files, hadn't tried with custom PIT's
- Also, I'm able to flash all kinds of bootloaders, but without any visible changes in phone
- I made my own JIG USB PLUG, but no matter how hard i tried, it didn't work (i'll try tomorrow with 301k, instead of 300k, but i think it's too small difference to work different)(+++ it didn't work even with older bootloader, even with two types of turning off the phone)
- Phone is recognized by system as Samsung Device, but after bootscreen stucking, it changes to an unknown device.
- Flashing kernel ends up with boot.bin and stucks
- Flashing other stuff ends up with NAND Write Start!! or zImage etc.
- I tried all versions of Odin.
I'm getting tired after 4 days, and nights of trying to rivive that screwsung (sry, i'm really mad )
So, again: What am I supposed to do? Any ideas?
Thanks in advance,
CU tomorrow!
Click to expand...
Click to collapse
Let's start with a model number. It'll be on the label underneath the battery.
ctomgee said:
Let's start with a model number. It'll be on the label underneath the battery.
Click to expand...
Click to collapse
Model number? You mean GT-I9100 or what? I thought it's obvious, so i didn't mention that...
+ I got the IMEI (I feel like an idiot, forgot it is sticked under battery) - first two digits: 35 (someone in some thread found it useful, so maybe it will be useful again)
celu said:
Model number? You mean GT-I9100 or what? I thought it's obvious, so i didn't mention that...
+ I got the IMEI (I feel like an idiot, forgot it is sticked under battery) - first two digits: 35 (someone in some thread found it useful, so maybe it will be useful again)
Click to expand...
Click to collapse
Not so obvious, really. I've seen more people I can count who have different models of SII come to this forum and flash random I9100 stuff to their SGH-I777/SGH-I727/SGH-T989/SPH-D710/SCH-R760/whatever.
Anyways, if you can get to download mode, just try flashing an original Samsung stock firmware. I recommend 4.0.3 or earlier. You can download one from www.sammobile.com.
Also, you said you can flash all sorts of PIT files. What PIT files? If you happened to flash a PIT file NOT meant for an I9100, you may have screwed the pooch.
ctomgee said:
Not so obvious, really. I've seen more people I can count who have different models of SII come to this forum and flash random I9100 stuff to their SGH-I777/SGH-I727/SGH-T989/SPH-D710/SCH-R760/whatever.
Anyways, if you can get to download mode, just try flashing an original Samsung stock firmware. I recommend 4.0.3 or earlier. You can download one from (link).
Also, you said you can flash all sorts of PIT files. What PIT files? If you happened to flash a PIT file NOT meant for an I9100, you may have screwed the pooch.
Click to expand...
Click to collapse
I mean, PIT files of the same type, but from different sources (each one was meant for an I9100)
I tried that one, stucks at NAND Write Start!!... Maybe I'm doing something in wrong order?
I need to go to sleep, really, I don't want to screw something up because of my tiredness. I'll be back in a few hours, and for the moment, thanks for help
celu said:
I mean, PIT files of the same type, but from different sources (each one was meant for an I9100)
I tried that one, stucks at NAND Write Start!!... Maybe I'm doing something in wrong order?
I need to go to sleep, really, I don't want to screw something up because of my tiredness. I'll be back in a few hours, and for the moment, thanks for help
Click to expand...
Click to collapse
We have the same model of SGS2 and tried the same. It also stucks in the bootscren.
celu said:
I mean, PIT files of the same type, but from different sources (each one was meant for an I9100)
I tried that one, stucks at NAND Write Start!!... Maybe I'm doing something in wrong order?
I need to go to sleep, really, I don't want to screw something up because of my tiredness. I'll be back in a few hours, and for the moment, thanks for help
Click to expand...
Click to collapse
I'd also make sure your cable is good, and is connected directly to a port on the computer instead of through a USB hub, or a port on your keyboard, monitor, or other pass-through port.
Hello again.
I've just came home, and first of all, I've tried a few wires, all original, two from Nokia, one from HTC, two from Sony Ericsson, all with the same result.
One thing I want to ask you is that i don't really know which thing i need to flash first, kernel or firmware.
As far as i know flashing ICS Kernel with Gingerbread firmware may cause softbrick, or even hardbrick.
I've tried everything you said and I'm still stuck.
Thanks for your replies.
celu said:
Hello again.
I've just came home, and first of all, I've tried a few wires, all original, two from Nokia, one from HTC, two from Sony Ericsson, all with the same result.
One thing I want to ask you is that i don't really know which thing i need to flash first, kernel or firmware.
As far as i know flashing ICS Kernel with Gingerbread firmware may cause softbrick, or even hardbrick.
I've tried everything you said and I'm still stuck.
Thanks for your replies.
Click to expand...
Click to collapse
Firmwares will contain a kernel. Thus, if you want a custom kernel, you would have to flash a firmware first, then the custom kernel. Otherwise, if you do it in the reverse and flash a custom kernel first, then the kernel contained in the firmware would overwrite the custom kernel.
And you are correct that you cannot use ICS kernels with GB, or GB kernels with ICS.
Try following the instructions in this thread for the original I9100 model: http://forum.xda-developers.com/showthread.php?t=1457458. They are the first two sets of instructions labelled "GINGERBREAD VERSION" and "ICS VERSION". I would try the ICS version first.
ctomgee said:
Firmwares will contain a kernel. Thus, if you want a custom kernel, you would have to flash a firmware first, then the custom kernel. Otherwise, if you do it in the reverse and flash a custom kernel first, then the kernel contained in the firmware would overwrite the custom kernel.
And you are correct that you cannot use ICS kernels with GB, or GB kernels with ICS.
Try following the instructions in this thread for the original I9100 model: http://forum.xda-developers.com/showthread.php?t=1457458. They are the first two sets of instructions labelled "GINGERBREAD VERSION" and "ICS VERSION". I would try the ICS version first.
Click to expand...
Click to collapse
Just to be sure: with Odin v.1.85?
celu said:
Just to be sure: with Odin v.1.85?
Click to expand...
Click to collapse
Any version of Odin should work fine, including 1.85, but I currently use Odin 3.04.
Odin is not recognizing my phone, v 3.04.
I'll try with older version.
EDIT:
Something is wrong with drivers, i'm reinstalling them, just a sec.
EDIT2:
Drivers are ok now, but:
Odin log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
EDIT3:
I was thinking about using Heimdall to flash, but is there any difference?
Is there any possibility to force flash kernel? Or even whole firmware?
celu said:
Odin is not recognizing my phone, v 3.04.
I'll try with older version.
EDIT:
Something is wrong with drivers, i'm reinstalling them, just a sec.
EDIT2:
Drivers are ok now, but:
Odin log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
Click to expand...
Click to collapse
So you never answered about the USB port - are you plugged directly into the computer? Have you tried other direct ports on the computer yet?
Last resort is to try a different computer altogether.
ctomgee said:
So you never answered about the USB port - are you plugged directly into the computer? Have you tried other direct ports on the computer yet?
Last resort is to try a different computer altogether.
Click to expand...
Click to collapse
I've got 3 USB ports (I'm using a laptop, also Samsung, if it matters), and tried all of them. Maybe I could be able to use PC tomorrow. Or i'll reinstall windows, because i'm using 64-bit version atm.
EDIT:
My father told me, that it could be broken "board to board header connector".. But i'm still trying!
EDIT2:
I've just had a small talk with samsung service manager, he told me that they had one phone that started to work after 24hours spent without battery. Seems a little bit silly, but why wouldn't i try?
EDIT3:
And so.. I'm loosing hope. JIG doesn't work, don't even turns on the phone. Kernel, or firmware can't be loaded at all.. I'm completely out of ideas.
Related
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Sent from my GT-I9100 using xda premium
insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.
insat3d said:
Hey Folks,
My phone is bricked. Here are the events before and after the crash.
Model: I-9100
I had installed CM10 ROM (ver. 25-Aug-2012) on my phone. It worked fine for a week and then while using the camera app, the phone froze. I restarted it, but it kept getting stuck at the boot logo. I could get into the download mode but not recovery. So I used ODIN to re-flash the same ROM, but ODIN got stuck at NAND write step. I tried it several times - changed the laptop - changed the cable - changed the ROM - nothing happened. Same thing, it either gets stuck at NAND or SBL.BIN.
I went through a lot of XDA pages and tried flashing the ICS stock ROM - same result - stuck at NAND/SBL. Tried both the 1-file and 3-file as well as the one with repartition (PIT) file. Nothing works. In case of repartition, it gets stuck at repartition step itself.
Also, over my last 5 tries the binary count is not changing. It is stuck at 13 and current binary shows as Samsung Official.
My warranty is not valid as I bought it in India but am in the US now. It's only 2 months old.
Summary: Download mode - Yes, Recovery Mode - No, NAND / SBL.bin fail, Stock ROM fail
Please help.
1) Have I hard bricked it?
2) Do I have to JTAG it? Any idea if anyone does it in Minneapolis? Or do I have to send it to "mobiletechvideos"?
3) I have a CWM recovery file on my external SD card. Is it of any use?
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLP7_I9100ODDLP9_I9100DDLPA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
Then it gets stuck here for more than half hr and i just unplug it.
Thanks
Click to expand...
Click to collapse
sounds to me like your internal storage is damaged. I guess it's a warrenty issue
alexkno said:
sounds to me like your internal storage is damaged. I guess it's a warrenty issue
Click to expand...
Click to collapse
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
UltimateAnas said:
It doesn't seem like a hard brick so that is kindo of lucky! However I have never cime across anyone with that problem! Why don't you try using odin to flash latest siyah kernel then try entering recovery and wipe data+cache and re-flash rom, hopefully it will work!
Click to expand...
Click to collapse
pilgrim011 said:
I have had the same problem few months ago. Finally, I have managed to kill it when I tried to flash the bootloader - it got stuck at the beginning (just like with everything else that I tried to flash - ROMs, kernels...), no more signs of life (no charging, no download mode, nothing), andd after that Samsung service center replaced the motherboard. I think that's the only way, but you may try everything before you send it for repair. There's a thread in this forum dedicated to unflashable phones, try to get help there.
Click to expand...
Click to collapse
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So the binary counter is not stuck as I had mentioned earlier. But it still got stuck at the NAND write step.
From what I understand, the kernel does change from "Samsung official" when I flash stock ROM to "Custom ROM" when I flashed Siyah and back to "Samsung official" when I re-flashed it. But it gets stuck after that. Any ideas why?
Thanks
insat3d said:
I hope it is not a warranty issue. I spoke to sammy (US), they said they don't cover warranty from outside US. (
Is there any way to confirm hardware damange??
But my phone is not dead. I am able to boot it into download mode. So I am guessing it is softbricked right? Also, i tried flashing Siyah kernel (latest and the one before). It updated the binary count. So it is not stuck as I had mentioned earlier.
Any other ideas guys?
Thanks
Click to expand...
Click to collapse
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
Jokesy said:
Visit this thread: forum.xda-developers.com/showthread.php?t=1457458
If your phone doesn't work after that, then it's as good as dead
Click to expand...
Click to collapse
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?
insat3d said:
I tried both ICS and GB mentioned on this link. It always gets stuck after zImage when I try without PIT file or set partition when I try partition.
Is JTAG going to be of any help here?
Click to expand...
Click to collapse
have you tried everything there?
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
Jokesy said:
have you tried everything there?
Click to expand...
Click to collapse
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
I don't think so. You might have to replace your motherboard.
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.78
GT I9100
Next phone: Galaxy NOTE II
insat3d said:
Yes, I did. I tried all possible combinations. I even tried the GB ROM.
I also tried Heimdall. It still gets stuck at the same place as ODIN. In both, the Kernel gets uploaded and then it just gets stuck indefinitely. (Heimdall crashes after a while).
Couple of ques:
1) If my NAND memory is corrupt. Can JTAG fix this?
2) If JTAG can't fix this and I were to try getting it repaired outside warranty. How much will it cost? Do I have to replace the entire motherboard?
I DONT have a valid warranty. Please let me know
Click to expand...
Click to collapse
if I am not mistaken JTAG will give access to core, but I guess (but I am not a technician) that if the internal storage is corrupted and not even repartition helps, then I guess only replacing it might help.
I'd advise to watch out for a repaircenter near you and ask
Ok...so the phone is 2 months old.....
Purchased in India but being used in the US?.......
I don't care what Samsung says.....it sounds to me like they are trying to 'fob you off'. I personally would take this further. ....contact Samsung HO, contact your local trading standards department (or whatever it's called).
No warranty. ....that's just corporate bulls**t.......the age of the phone (if it can be proved) is what's important.....I think you have a very strong case here.....go with it.
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Similar problem i9100T
I have the same problem in that the phone stops at nand write when attempting to install package. I can only get into download but it will flash a bootloader but that is all. I believe that it may be necessary to reload the .pit file but I cannot find where this would be found. I presume if this were included it would reinstall this and would fix the internal storage. Any advise on this would be gratefully received.
Galaxy S2 stuck at NAND WRITE START
MODS.... please delete this post.
Hi i've had CM9 in my phone for a half year now without any issues, however two days ago i woke up and went to check my phone, it froze and after that i haven't been able to boot it up, it just hungs at the samsung logo with the triangle and all that, so i've been trying to sort out this for two days straight now and i'm getting really sick of this, what i've done so far is:
* tried to flash alot of rom's and such with no success, stucks at: NAND Write Start!!
* tried to flash on a different computer
* tried to flash with different usb ports
Oh and i can't get into the recovery mode, only the download mode.
This is the files i've tried to flash and such to get my phone working again:
Kernel_I9100XXLPH
I9100XXLPQ_I9100HTSLP3_HTS
I9100XWLPG_I9100XXLPX_I9100NEELP4_NEE
I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar
I9100XWLPG_I9100NEELP4_NEE
GT-I9100_Kernel_Gingerbread-supercurio-3
GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4
cm-10-20120927-EXPERIMENTAL-i9100-jb_mali-changmin
cm-10-20120926-NIGHTLY-i9100
cm-9-20120330-ODIN-galaxys2.tar
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5
CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5
GT-I9100_NEE_I9100XWLPD_I9100XXLPW_I9100NEELP4
Please, can anyone try to help me? I can't explain how tired i am of this, i really need and want my phone to work again! Thanks
Emperia said:
Hi i've had CM9 in my phone for a half year now without any issues, however two days ago i woke up and went to check my phone, it froze and after that i haven't been able to boot it up, it just hungs at the samsung logo with the triangle and all that, so i've been trying to sort out this for two days straight now and i'm getting really sick of this, what i've done so far is:
* tried to flash alot of rom's and such with no success, stucks at: NAND Write Start!!
* tried to flash on a different computer
* tried to flash with different usb ports
Oh and i can't get into the recovery mode, only the download mode.
This is the files i've tried to flash and such to get my phone working again:
Kernel_I9100XXLPH
I9100XXLPQ_I9100HTSLP3_HTS
I9100XWLPG_I9100XXLPX_I9100NEELP4_NEE
I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar
I9100XWLPG_I9100NEELP4_NEE
GT-I9100_Kernel_Gingerbread-supercurio-3
GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4
cm-10-20120927-EXPERIMENTAL-i9100-jb_mali-changmin
cm-10-20120926-NIGHTLY-i9100
cm-9-20120330-ODIN-galaxys2.tar
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5
CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5
GT-I9100_NEE_I9100XWLPD_I9100XXLPW_I9100NEELP4
Please, can anyone try to help me? I can't explain how tired i am of this, i really need and want my phone to work again! Thanks
Click to expand...
Click to collapse
try flashing a stockfirmware which comes with a .pit file and see
Sun90 said:
try flashing a stockfirmware which comes with a .pit file and see
Click to expand...
Click to collapse
Could you please help me out, i'm not really sure where i can find that.
Edit: I live in Sweden, Europe so i need a nordic firmware.
Emperia said:
Could you please help me out, i'm not really sure where i can find that.
Edit: I live in Sweden, Europe so i need a nordic firmware.
Click to expand...
Click to collapse
check the link below read the main post(#1) of that thread and proceed carefully to revive back ur phone
http://forum.xda-developers.com/showthread.php?t=1457458
Sun90 said:
check the link below read the main post(#1) of that thread and proceed carefully to revive back ur phone
http://forum.xda-developers.com/showthread.php?t=1457458
Click to expand...
Click to collapse
Thanks, i've read that guide earlier and tried a few steps with no luck.
Is this what i should do?
"WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues "
Emperia said:
Thanks, i've read that guide earlier and tried a few steps with no luck.
Is this what i should do?
"WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues "
Click to expand...
Click to collapse
no dont mess with that 'Bootloader' one ma8, there is one on how to use pit file look into that
look for this in that thread
Recovering a soft bricked phone
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC and .PIT. Put each one in its place.
2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
Now here, take a breath
First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!
Sun90 said:
no dont mess with that 'Bootloader' one ma8, there is one on how to use pit file look into that
Click to expand...
Click to collapse
Hmm, well the only files i got when i downloaded the recovery package via that thread is:
MODEM_I9100XXLPH_REV_02_CL1104396.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar
I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar
GT-I9100-MULTI-CSC-OXALPH.tar
thanks for trying to help me, it's appreciated!
Emperia said:
Hmm, well the only files i got when i downloaded the recovery package via that thread is:
MODEM_I9100XXLPH_REV_02_CL1104396.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar
I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar
GT-I9100-MULTI-CSC-OXALPH.tar
thanks for trying to help me, it's appreciated!
Click to expand...
Click to collapse
did u dwnld'd that file under Gingerbread or ICS?
Sun90 said:
did u dwnld'd that file under Gingerbread or ICS?
Click to expand...
Click to collapse
The ICS one, is that wrong?
Emperia said:
The ICS one, is that wrong?
Click to expand...
Click to collapse
yes its correct, The ICS one is the right one for u
now follow the instruction over that thread for where to put those files in ODIN and flash the same
Sun90 said:
yes its correct, The ICS one is the right one for u
now follow the instruction over that thread for where to put those files in ODIN and flash the same
Click to expand...
Click to collapse
Alright, we'll see what happens, there is no pit file thought, correct?
Emperia said:
Alright, we'll see what happens, there is no pit file thought, correct?
Click to expand...
Click to collapse
its only needed in the worst case scenerio
Sun90 said:
its only needed in the worst case scenerio
Click to expand...
Click to collapse
Ah alright, so i should put all those files even the bootloader in odin and try to flash? Just making sure!
Emperia said:
Ah alright, so i should put all those files even the bootloader in odin and try to flash? Just making sure!
Click to expand...
Click to collapse
yes
ps- and remember that u r doing all this thing at ur own risk, do not complain in the Future if something goes wrong there
Sun90 said:
yes
Click to expand...
Click to collapse
This is what happens:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.bin
<ID:0/006> NAND Write Start!!
Emperia said:
This is what happens:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.bin
<ID:0/006> NAND Write Start!!
Click to expand...
Click to collapse
do u see a red 'fail' message in the big rectangle box in odin
Sun90 said:
do u see a red 'fail' message in the big rectangle box in odin
Click to expand...
Click to collapse
Nope, it just seems like it's stuck, this is what always happens, i never get fail messages or such.
Emperia said:
Nope, it just seems like it's stuck, this is what always happens, i never get fail messages or such.
Click to expand...
Click to collapse
which version of windows ur using is it XP or 7
Sun90 said:
which version of windows ur using is it XP or 7
Click to expand...
Click to collapse
Windows 7, i've tried to flash on windows xp as well, and it gets stuck too, no fail error.
Emperia said:
Windows 7, i've tried to flash on windows xp as well, and it gets stuck too, no fail error.
Click to expand...
Click to collapse
try to reflash using the PIT file att below, extract the file put it in the pit section on odin along with the other files in there respective section also check the re-partition and see
Ok so last night my phone froze up while I was browsing the web (it froze just after rotating, if that's of any significance) so I held the power button down until it turned off. Trying to turn it on again, it just sat at the galaxy s 2 logo before any bootanimations etc start playing.
I thought I'd try to just re-flash the ROM (CM10 nightly 26/9/2012) and it seemed to just freeze up near the end of the flash, so I left it to do it's thing.
When I returned to the phone, it was showing me a kernel panic screen, so I held the power button to turn it off again and since then it won't boot into the ROM, it won't boot into recovery, and until just now it wouldn't be recognised by odin in download mode.
I had tried installing the USB drivers for the phone etc and it wouldn't work, however while writing this topic I just got a notification on my PC saying USB drivers had been installed and Odin seemed to recognise my phone, so I tried flashing cm9 resurrection, however it seems to be stuck. These are the messages in Odin, for reference:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.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> zImage
<ID:0/003> NAND Write Start!!
and it's just been stuck there since I pressed start. There is no progress bar or anything on the phone either. Oh, and Odin's progress bar thing at the top just says "KERNEL" with a blank bar under it and "0:[com3]" with a yellow background below that.
Is it safe to unplug the phone and try again with a different USB cable?
EDIT: After trying different methods to recover it (with the same result from Odin):
Orkane1989 said:
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Click to expand...
Click to collapse
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
So it's safe to unplug the phone?
D3_ said:
So it's safe to unplug the phone?
Click to expand...
Click to collapse
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
Try reflashing kernel then flash ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Orkane1989 said:
Yes I have done it before. You just won't have a ROM on your device. Just put it back into download mode and try the kernel first before ROM.
Sent from Jelly Fuelled SGS2
Click to expand...
Click to collapse
Just tried this, getting the same thing, Odin gets the first "bar" in the progress bar completed and seems to get stuck. Same output as above.
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
You will have to consult someone with some more knowledge about this than me. You could have a corrupt data partition... but its honestly out of my league now lol. Sorry I couldn't help.
Sent from Jelly Fuelled SGS2
Orkane1989 said:
When the first bar completes that (from what I remember) is just Odin unpacking the files to flash to device. Once it does that it checks that its on there properly which is by comparing md5, then it send a command to run the kernel.
Seems like your phone is unable to do even that.
Click to expand...
Click to collapse
According to the output it gives me (in the OP) it does successfully check the MD5 though.
I'll admit, I haven't actually used Odin since I first rooted this phone (back in december last year) so I'm back to knowing basically nothing about how it works.
Yes it does confirm the md5
But after that it sends the commands to start running the new kernel (basically installing it on the device firstly)
Which is where it gets stuck.
Sent from Jelly Fuelled SGS2
Just tried this: http://forum.xda-developers.com/showthread.php?t=1457458
Same issue with flashing those files.
I don't want to try the .pit because if it doesn't flash then I'll be pretty f*cked, right?
I would try what ever else you could find because if you get that guide wrong you could end up turning your phone into a paperweight. But if you so have to use the guide take note that you ahould try flashing the files WITHOUT .pit or repartition first. If that doesn't succeed than your last option is to use the .pit file and repartition.
Sent from Jelly Fuelled SGS2
I did try it, without the .pit/repartition as the guide says to try it without it first, but again, it won't flash anything (which is why I don't think I'll try the .pit/repartition)
I wouldn't risk it. Does definity sound like a dodgy data partition. You should post in that guide explaining your situation. Somebody who know more than me should be able to give you a few options.
Sent from Jelly Fuelled SGS2
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, I hope someone can help me out here, Samsung's online help sure wasn't a big help. Trying to get my hands on the stock image for the SGH-i857 a got a little over zealous trying to clear out some of the stock APKs and was hoping to roll it back to stock.
If you have a windows machine try downloading Samsung Kies with your DoubleTime connected. Try to update the firmware/software and it should revert it back to stock.
I do have an Odin flashable I can give you if that doesn't work, but I would compress it with 7zip in order to put it on the Forum.
Legojr said:
If you have a windows machine try downloading Samsung Kies with your DoubleTime connected. Try to update the firmware/software and it should revert it back to stock.
I do have an Odin flashable I can give you if that doesn't work, but I would compress it with 7zip in order to put it on the Forum.
Click to expand...
Click to collapse
I did try the kids method with no luck, I would love to try the Odin flash for the phone. If you don't feel like uploading it to the forums I'd be happpy to PM you my gmail.
Here is the link: https://www.dropbox.com/s/p3dj426vdav4nsp/I857UCKI1-I857UCKI1-I857UCKI1-HOME.tar.md5
I had to put it on Dropbox because it was so big.
It is recommend that you use Odin v1.85, this however is not tested. I might be testing it soon though.
To put a DoubleTime into download mode you need to hold the volume up and powerb button at the same time from a completely off state.
I wish you luck.
Has anyone found a way for fully flashing the double time to stock? I accidentally flashed an update.zip file from another phone and now wifi and bluetooth are not working. Hopes fast answers-
migui0401 said:
Has anyone found a way for fully flashing the double time to stock? I accidentally flashed an update.zip file from another phone and now wifi and bluetooth are not working. Hopes fast answers-
Click to expand...
Click to collapse
Really? The thread has 4 other posts and the one right above yours has the file you need.
es0tericcha0s said:
Really? The thread has 4 other posts and the one right above yours has the file you need.
Click to expand...
Click to collapse
Man, i don't if you're up to date, but the double time has a firmware problem which conflicts with download mode and it's almost impossible to flash it. That's why my question, have you been able to flash? Please, i need help.
PD: i have the stock firmware and have used almost all compatible odin versions with this device without success.
migui0401 said:
Man, i don't if you're up to date, but the double time has a firmware problem which conflicts with download mode and it's almost impossible to flash it. That's why my question, have you been able to flash? Please, i need help.
PD: i have the stock firmware and have used almost all compatible odin versions with this device without success.
Click to expand...
Click to collapse
They don't sell the Doubletime around here, so wouldn't have a way to be up to date with it. Why don't you describe what's happening via Odin when trying to flash instead of just saying it didn't work, which is not very helpful.
es0tericcha0s said:
They don't sell the Doubletime around here, so wouldn't have a way to be up to date with it. Why don't you describe what's happening via Odin when trying to flash instead of just saying it didn't work, which is not very helpful.
Click to expand...
Click to collapse
This all what happens in odin, it stays stuck on Setup Connection...
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I857UCKI1-I857UCKI1-I857UCKI1-HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
migui0401 said:
This all what happens in odin, it stays stuck on Setup Connection...
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I857UCKI1-I857UCKI1-I857UCKI1-HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
Click to expand...
Click to collapse
I didn't realize that the Doubletime was an ATT phone. Have never seen one or had one brought by my shop. *shrug* Is yours ATT branded or GoPhone? It's possible the firmwares aren't compatible between the different versions... Or that being of that vintage Samsung, maybe the program Heimdall might have more luck a la the Samsung Galaxy S 4g from T-Mobile.
Is the version you are trying to install as newer or newer than the current firmware found on the phone?
Tried different cords?
Different ports on the PC?
Does it show up once or twice in the COM boxes of Odin?
Are you running Odin as admin?
Edit: Found other posts on other forums where it gets stuck at the same step, so guess it's a thing. Found in both Chinese and Spanish phone forums.
es0tericcha0s said:
I didn't realize that the Doubletime was an ATT phone. Have never seen one or had one brought by my shop. *shrug* Is yours ATT branded or GoPhone? It's possible the firmwares aren't compatible between the different versions... Or that being of that vintage Samsung, maybe the program Heimdall might have more luck a la the Samsung Galaxy S 4g from T-Mobile.
Is the version you are trying to install as newer or newer than the current firmware found on the phone?
Tried different cords?
Different ports on the PC?
Does it show up once or twice in the COM boxes of Odin?
Are you running Odin as admin?
Edit: Found other posts on other forums where it gets stuck at the same step, so guess it's a thing. Found in both Chinese and Spanish phone forums.
Click to expand...
Click to collapse
-Odin always opens with admi rights.
-Yes, i've tried all ports on my pc.
-It's the same firmware.
-It shows just once in COM BOX.
Can you help?
Doesn't seem like there is a readily available solution, as your issue seems to be shared by others without any posted fix I could find here, or in the other phone forums. Sorry. Like I said earlier, you could try the Heimdall tool, but other than that, haven't the slightest. Older Samsungs suck because of issues like this - limited Odin support. Have you tried Kies too?