hey guys, had the gs2 a few months now and decided to root it tonight.
plan back fired. stuck with the samsung logo and the ! symbol.
original info:
GT-I9100
2.3.3
I9100NEKF2
2.6.35.7-I9100XWKF4-CL280512
[email protected]#2
Gingerbread.XWKF4
Click to expand...
Click to collapse
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4
is what i tried to flash this with (odin).
Went through all the steps. flashed, blue bar came across. said success in ODIN. Phone rebooted but wont get past the ! screen.
have tried flashing with I9100XWKF4_Kernel and tried reflashing with CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4, Both result in same issue (phone stuck on boot screen with ! symbol).
Any ideas on where ive gone wrong? or possibly a way to resolve this?
Thanks again
rossonza
can you enter download or recovery mode? (volume up + home + power // volume down + home + power)
If you can go in recovery, wipe data/cache factory reset + wipe cache + advanced and wipe dalvik cache.
Mount usb storage and put in your internal memory a rom (like batista or villain rom or checkrom your choice, i use batista) flash that one and reboot.
If you can only go in download mode, try to flash the lite'ning 6.1 (KH3) rom, be sure to DONT check repartition (that will brick your phone).
The lite'ning already contains root (no need to use cf-root before) so if you can enter download mode, it's a good choice to "unlock" (hopefully it works) your phone.
i can get into download mode still but cant get into recovery (never could?)
downloading that rom now. big download :S
Well, the rooting process didnt worked well if you cant even enter recovery (that comes with the rooted kernel).
Keep me informed if you can fix the problem.
I forgot to tell you, you can also flash from download (maybe you prefer) a stock original rom (from this forum, S2 Android Original Development) so you get back to the stock rom (without root).
im downloading both the custom liteneing rom and the stock firmware. Ill let you know how it goes.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Litening wont flash.
<ID:0/003> Added!!
<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> Sbl.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
GT-I9100_H3G_I9100XWKF4_I9100NEKF2_I9100H3GKF1
That's not looking bright.
Im sure it can be fixed since you can enter dw mode and Odin finds / connect at the phone.
Try with the stock one, if also that one isnt working, you need a more experienced advice from a "veteran" of the forum
Stock not flashing either, both failed :S
really hope i havnt destroyed this phone. nexus one was a breeze to root.
phone gets into download mode no issues and ODIN picks it up.
rossonza said:
i can get into download mode still but cant get into recovery (never could?)
downloading that rom now. big download :S
Click to expand...
Click to collapse
If (never could?) means also on stock firmware then this was the first mistake.You need to try and flash your original FW (or another from XDA if your phone is unlocked) to get recovery.Without it you wont root or install ROMs.
http://www.multiupload.com/N5RWCXT1LJ
i imagine youve already got it but stick it in pda and try it.It might take a few trys but give it few goes.I had an i9000 jtaged that came back without recovery mode and it took me a few failed attempts before it finally passed and rebooted with recovery and then your away laughing.
and if it continues to fail? jig and return to samsung? or will this be covered under my 3 contract..
If your download count (download mode) is set to 0, it is covered by your warranty.. if it's more than 0, you need a jig to set it to 0.
Kinda strange problem you got here, phone is not bricked (since odin find it and you can access dw mode) but looks like it refuse any kind of firmware.
Anyone else a suggestion? im sure big names of the forum can help out a bit here...
rossonza said:
and if it continues to fail? jig and return to samsung? or will this be covered under my 3 contract..
Click to expand...
Click to collapse
Heres the problem with the return idea.If the symbol on the screen is the classic "PHONE...!...PC" icon then its a semi-bricked icon and if your bin counter is at 0 then samsung are your better choice but 3 might not be abligated to take it back as this sign clearly means a PC-Phone connection problem and not a software problem alone.If the icon on your screen is a big yellow triangle with the ! inside then samsung can refuse to take the phone back even if your bin counter is at 0 cos this is a special warning sign put but samsung to see if you have been screwing with your phone outside of your warranty.If its the big yellow one then keep trying to flash and if nothing works then pay 30 or 40 bucks to get a jtag done.Because you can get into download mode I see no reason at the moment why it wont flash Use the firmware from XDA dont forget.IT worked for me with their PDA flashes and not the samfirmware files with pit files.Dont use pit files and try a more reciente FW if your phone is unlocked as i said ealier.If you want try the samfirmware file that gives you the 3 files instead of one(without pit but use odin 1.85 from here http://forum.xda-developers.com/showthread.php?t=1075278
PDA/PHONE/CSC and see what happens.give everything a try.
try this if you want.Its XWKE1 multi CSC H3GKD4 from May.Thought it might help cos its an H3G brand firmware like on your phone.If it works then yourll get back recovery and then can flash what ever you want again.Worth a try.BUT use Odin from XDA (1.85) and no pit file and dont tick re-partition.PDA/PHONE/CSC
password is samfirmware.com
http://hotfile.com/dl/119477273/436e381/I9100XWKE1_H3GKD4_NEKD5.rar.html
rossonza said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.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> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Litening wont flash.
Click to expand...
Click to collapse
You can't flash a custom rom with odin.
You need CMW.
That's why failed.
Red_Vex said:
You can't flash a custom rom with odin.
You need CMW.
That's why failed.
Click to expand...
Click to collapse
Wrong, Lite'ning package is a ODIN package, not a clockworkmod package, i did flash the rom 3-4 times in the last 2 months with odin.
keep trying to flash, but its failing. may be a gonner :S i always read that its not bricked if you can get to download mode. guess this is wrong?
im getting no phone to PC error. so is all ok?
Download mode shows current binary as custom
6 counts of flashing the device.
rossonza said:
keep trying to flash, but its failing. may be a gonner :S i always read that its not bricked if you can get to download mode. guess this is wrong?
im getting no phone to PC error. so is all ok?
Download mode shows current binary as custom
6 counts of flashing the device.
Click to expand...
Click to collapse
Download mode does not mean its bricked or not bricked it just means on a bricked phone you stand a chance of recovery but that depends upon a number of factors the principle one in all this flashing is the user .
It may that multiple flashings have messed up or that the wrong firmware has been flashed .
My steps would be .
One reset rom counter with USB jig to clear for warranty.
Two Recovery mode Mounts and storage Format data cache system dalvik and sd card .
Power off boot to download mode and flash a full stock rom via Odin .
Do not use any firmware you have already used .
jje
recovery mode isnt available so cant mount.
anyone else care to input?
cooza said:
Heres the problem with the return idea.If the symbol on the screen is the classic "PHONE...!...PC" icon then its a semi-bricked icon and if your bin counter is at 0 then samsung are your better choice but 3 might not be abligated to take it back as this sign clearly means a PC-Phone connection problem and not a software problem alone.If the icon on your screen is a big yellow triangle with the ! inside then samsung can refuse to take the phone back even if your bin counter is at 0 cos this is a special warning sign put but samsung to see if you have been screwing with your phone outside of your warranty.If its the big yellow one then keep trying to flash and if nothing works then pay 30 or 40 bucks to get a jtag done.Because you can get into download mode I see no reason at the moment why it wont flash Use the firmware from XDA dont forget.IT worked for me with their PDA flashes and not the samfirmware files with pit files.Dont use pit files and try a more reciente FW if your phone is unlocked as i said ealier.If you want try the samfirmware file that gives you the 3 files instead of one(without pit but use odin 1.85 from here http://forum.xda-developers.com/showthread.php?t=1075278
PDA/PHONE/CSC and see what happens.give everything a try.
try this if you want.Its XWKE1 multi CSC H3GKD4 from May.Thought it might help cos its an H3G brand firmware like on your phone.If it works then yourll get back recovery and then can flash what ever you want again.Worth a try.BUT use Odin from XDA (1.85) and no pit file and dont tick re-partition.PDA/PHONE/CSC
password is samfirmware.com
http://hotfile.com/dl/119477273/436e381/I9100XWKE1_H3GKD4_NEKD5.rar.html
Click to expand...
Click to collapse
Thanks that firmware fails, Whats a JTAG?
i dont mind paying to get this fixed if thats what it comes to.
cheers
Why not try to re-install the drivers?
I got problem flashing the rom, but rectified it after re-installing the drivers.
May help u.
Related
Hi all. I thing my phone is struggeling to survive.
First I'll give you some background info:
Phone is SGS3 I9300.
[ROM] Has been running Omega Rom since one of the first versions. Been running v32 since it was released (not v32.1)
[Kernel] Been running Omega's tweaked stock kernel most the time, but installed SiyahKernel 1.7rc3 some days ago.
About a week ago I recieved a 64gb SanDisk MicroSDXC card and installed Mittiadj's ExtSD2InternalSd script.
[recovery] CWM V6.0.1.2
So, what happened?
Well, when I installed the extsd2internal it wouldn't apply on boot, so per his guide, I installed Script Manager and got it working.
Some days ago I wiped system, flashed omega 32, flashed siyah kernel and flashed the extsd2internal for custom kernels.
Now the script worked without script manager.
After I installed Siyah, the phone reboted twice, about a day or 2 apart. The 3rd time it rebooted automatically, it did not manage to boot again (stopped at the Siyah boot logo,the purple eye).
From here, I switched the phone off, and using vol-up+home+power, I am SOMETIMES able to get into recovery. However, in recovery, I am able to flash cache but not dalvik, I tried flashing Omega, but it froze during the install wizard, I tried wiping system (for another attempt at Omega) but it rebbots then also.
Now the phone only gets to the White Samsung logo or to recovery (but recovery only shows version and the text)
E: can't mount /cache/recovery/command
Click to expand...
Click to collapse
If I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
Click to expand...
Click to collapse
Where can I go from here?
What has gone wrong?
I am suspecting the memory chip is fubar, but hope someone can tell me otherwise
For the record, I have tried booting with and without sim and microsd, no change comes from that.
In the mean time I guess it's time to resurrect the god'ol Nexus One
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
>>>>>>
f I hold vol-down+home+power, I get to a question if I want to install Custom ROM, vol down for cancel, up for yes. Pressed down.
Quote:
Warning!! A custom OS can cause critical....
If you want to download a custom OS, press the volume up key, otherwise, press volume down
This reads as totally bolocksd firmware and recovery .
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
jje
jje
Click to expand...
Click to collapse
JJEgan said:
Requiem87 said:
Hi all. I thing my phone is struggeling to survive.
Remove SD card and format it in windows as FAT 32 .
Boot to download mode and flash stock rom via Odin as alternative is a non warranty repair .
Click to expand...
Click to collapse
Tried flashing CWM via ODIN, but get an error after Writing stage. (i shoulden't have done that, because before the flash counter was 0, and it showed stock, after it shows as modified
Any reason to believe that flashing a stock rom will work better than flashing CWM?
Click to expand...
Click to collapse
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
JJEgan said:
Confused flashed CWM >> do you mean root ???
Stock rom has a kernel and would at least be on the right road for a warranty repair .
jje
Click to expand...
Click to collapse
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Requiem87 said:
Phone is allready rooted, as i had Omega Rom installed.
CWM means ClockWorkMod Recovery. I allready had that installed to, but as i wrote in first post, I had trouble getting it into recovery mode.
Nothing's changed in that regard tho
Update:
Tried flashing a stock rom via Odin, and this is the error message I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLJ4_I9300TENDLJ3_I9300XXDLID_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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
not looking so good - I think I would have another go at flashing stock - my AV/ firewall sometime stop odin trying disabling them - I suspect it wont help but hopefully it will
Hey Guys,
I've been trying to fix my s3 by using the popular method of flashing the official Samsung ROM by using Odin but every time i try to flash it Odin gets stuck at system.img:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMD2_I9300OXXEMD1_I9300XXEMC2_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> tz.img
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
The phone has installed custom recovery but it has no recovery image so i need to flash it using Odin but the problem is that it doesnt want to continue flashing. I can get to the download screen no problem on top it says : Odin MODE Product name Gt-i9300 Custom Binary Download Yes (1 counts) Current Binary Custom and System Status Custom . I've tried a few samsung roms but with no luck every time i get the fail message after system.img in Odin. I hope there is a fix , as far as i know if the phone can get to download mode it can be fixed so i hope you guys can provide me with a noob proof way of fixing it .
Thank You in advance
(further about the phone it has installed : clockworkmod recovery 6.0.2.7 , the phone is bought from Ireland )
can any one help or is the phone totally gone :?
Reads as either a faulty firmware file or damaged Nand or even not an I9300 .
TRY
http://forum.xda-developers.com/showthread.php?t=1978840
Fails you may need to buy a new motherboard .
jje
JJEgan said:
Reads as either a faulty firmware file or damaged Nand or even not an I9300 .
TRY
http://forum.xda-developers.com/showthread.php?t=1978840
Fails you may need to buy a new motherboard .
jje
Click to expand...
Click to collapse
i'm going to try and see what happens.
as far as the motherboard thing goes , how much does it cost to buy it and get it replaced
I tried the above method but Kies wont connect to my phone it stays on connecting. The only way to get it even there was when i put the phone in to Download Mode
motherhood is about $300
Glebun said:
motherhood is about $300
Click to expand...
Click to collapse
so if it ends up being the worst case scenario im better off buying a new phone.
As far as i've read around the forum if i can get into recovery and download mode apparently the phone can be fixed . I'm just hoping that someone can give me some pointers on where to go from here and how to flash the stock rom when odin fails
No Odin and no recovery ???
Or recovery
JJEgan said:
No Odin and no recovery ???
Or recovery
Click to expand...
Click to collapse
Here's the thing the phone boots into recovery no bother same with Download Mode. The phone battery fell out during the installation of a custum rom and thats how i got into this mess.
Flash custom rom via CWM recovery .
http://forum.xda-developers.com/showthread.php?t=1868004
jje
JJEgan said:
Flash custom rom via CWM recovery .
http://forum.xda-developers.com/showthread.php?t=1868004
jje
Click to expand...
Click to collapse
i haven't tried this method yet . Thank you ill try it when i get home later tonigh and update if it worked .
Cheers
1mpressioN said:
so if it ends up being the worst case scenario im better off buying a new phone.
Click to expand...
Click to collapse
yeah, and you can sell the phone for parts. and of course I meant motherboard, not motherhood, stupid auto correct
I9300 bricked
already flashed the custom recovery but phone won't go into recovery volume up, home key and power I can see a red exclamation symbol instead of rebooting recovery
I own a Orange Samsung S2 i9100 handset. This was working without problem until this morning where it was stuck on bootscreen. Recovery mode does not work.
I tried to update firmware using Odin 3.07 however this does not work. It fails to install.
I am now stuck with the message "Firmware upgrade encountered an error".
I cannot access SD card so rooting etc seems unlikely.
Any ideas?
Win 8 Machine
i9100
ORA-I9100XWLSY-20130606160421
Check out @Hopper8 thread about odin :thumbup:
Thanks.
I assume you are referring to this thread ( [GUIDE][Troubleshoot a failed Odin flash] )?
http://forum.xda-developers.com/showthread.php?t=2345831
I have tried recovering with the two most applicable firmware packages below. I do not know what others to try. I don't think I can use custom packages as I cannot access my SD Card?
http://www.sammobile.com/firmwares/2/
GT-I9100 Galaxy S II
PDA: I9100XWLSY
CSC: I9100ORALS8
MODEM: I9100BVLS4
Added: 2013-06-05
GT-I9100 Galaxy S II
PDA: I9100XWLSW
CSC: I9100XEULS5
MODEM: I9100XXMS2
Added: 2013-05-29
Odin does recognize my phone but each PDA update fails... Kies is installed but not running. Phone still can only go download mode and due to failed Odin update now shows no boot screen (only firmware fail message). I cnanot restore on Kies as did not use this PC before with phone.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSY_I9100BVLS4_I9100ORALS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.. *** At this point I click start
<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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
andrewwright said:
Have you tried to flash philz for recovery? May mount sd on flash. Or may be alliance rom does a tar version of its rom. Maybe that mite work. Dif version of odin may work to. Cable, reinstall drivers. What have you tried?
Click to expand...
Click to collapse
I have tried philz recovery steps however this also fails in Odin.
I have tried different usb ports and reinstalling drivers. However Odin can see the phone, so it may not be a USB driver/port issue.
The biggest hurdle is getting Odin to run the flash.
<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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1) *** Odin fails...
Original cable used? Have you read and tried all of whats in that thread?
andrewwright said:
Original cable used? Have you read and tried all of whats in that thread?
Click to expand...
Click to collapse
Original Samsung Cable.
Followed instructions in this thread using md5 files for i900?
http://forum.xda-developers.com/showthread.php?t=2201860
Odin packages instructions: Samsung Only
They come in the form of .tar.md5 file
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into main system and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing the 3 buttons combo to for a reboot into recovery.You should see the new CWM
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
to remove yellow triangle, use TriangleAway
Click to expand...
Click to collapse
Whatever I do, Odin still seems to fall over at same place.
What do I need to perform a full factory reset? I take it use Odin to install firmware?
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Sent from a galaxy far, far away
Hopper8 said:
Try flashing JB leak firmware. It's a 3-part firmware which will wipe as it flashes. Google 'JB leak i9100 Samfirmware', it should be the first link.
Click to expand...
Click to collapse
This doesn't work. I have assumed from your suggestion that I use Odin to install firmware via Odin. This fails as well.
I now have a new SD Card I could use to load any software onto the device. However I can not get to the recovery mode screen at all (only download mode). Therefore have no idea what to do now!
I also think my phone is worse now - on download mode screen:
ODIN MODE
PRODUCT NAME: GT-I9100
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: CUSTOM
Click to expand...
Click to collapse
What guide should I use to completely factory reset the phone?
How do I check if the phone memory is correctly partitioned?
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
dmuk said:
Tried Odin and Kies to restore; and same issues as above. Feels like time for a new phone...
Click to expand...
Click to collapse
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
niksyspidy said:
bro try the other odin version .....this happens to me once .....
remove the battery ,move to download mode , open odin, attach the phone before inserting the rom file in odin......
then flash it with crossed fingers......good luck:good:
Click to expand...
Click to collapse
What version? I have tried 1.85, 1.87, 3.04, 3.07 - all fail.
Can I use Kies to repair if I have not previous Kies backups?
Hi, currently having problems with S3 GT-I9300. I am stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.' Cannot do anything with phone atm. I have tried kies to carry it emergency recovery but that fails everytime it gets to 4%. I have also tried to flash a stock rom using Odin but that again says FAIL in red. Any help would be great! thanks
ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF1_I9300TMUEMF1_I9300BVEMF1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
John90uk said:
Hi, currently having problems with S3 GT-I9300. I am stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.' Cannot do anything with phone atm. I have tried kies to carry it emergency recovery but that fails everytime it gets to 4%. I have also tried to flash a stock rom using Odin but that again says FAIL in red. Any help would be great! thanks
ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF1_I9300TMUEMF1_I9300BVEMF1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to enter download mode and again flash the rom. You said "I also tried flashing STOCK rom", what were you flashing before? I just encountered this error today and flashed again after entering download mode and the error went away.
haiderijaz said:
Try to enter download mode and again flash the rom. You said "I also tried flashing STOCK rom", what were you flashing before? I just encountered this error today and flashed again after entering download mode and the error went away.
Click to expand...
Click to collapse
i have tried this on many occasions but i still receive the same errors in odin and kies. have also tried different ports ad pc's. how do i find the correct firmware for my phone?
You do not say what you where doing/ flashing in the first instance .
Kies must be off if using Odin .
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
JJEgan said:
You do not say what you where doing/ flashing in the first instance .
Kies must be off if using Odin .
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
Click to expand...
Click to collapse
The problem started when i plugged my phone on charge, when i unplugged it the phone turned off and continued to restart after samsung logo screen. I then tried kies to upgrade and initiliase but when that reached 4% it would say an error occured. This happens constantly. I then closed kies and tried flashing a Stock rom with ODIN but it keeps saying FAIL in red.
Also afrer kies recovery it now says firmware upgrade encountered an error.
John90uk said:
i have tried this on many occasions but i still receive the same errors in odin and kies. have also tried different ports ad pc's. how do i find the correct firmware for my phone?
Click to expand...
Click to collapse
I am unable to understand how you are using Kies and Odin at the same time. You need to go to sammobile.com and find your country there.
haiderijaz said:
I am unable to understand how you are using Kies and Odin at the same time. You need to go to sammobile.com and find your country there.
Click to expand...
Click to collapse
I am not using both softwares at the same time. Its a GT-I9300.
John90uk said:
I am not using both softwares at the same time. Its a GT-I9300.
Click to expand...
Click to collapse
First of all, Please try and make sure you can enter recovery mode. From what I understand, your phone is soft bricked. Also you mentioned the model. To download the appropriate firmware you need the country.
IF you can enter recovery mode, things are okay. We can then try rooting your phone with and flashing a custom rom. If that works, stock rom can be flashed back later. But first of all please try entering recovering mode by pressing Volume Up, Home and Power Button. When you see the samsung boot logo, let go and if you get some options that means you are in recovery.
haiderijaz said:
First of all, Please try and make sure you can enter recovery mode. From what I understand, your phone is soft bricked. Also you mentioned the model. To download the appropriate firmware you need the country.
IF you can enter recovery mode, things are okay. We can then try rooting your phone with and flashing a custom rom. If that works, stock rom can be flashed back later. But first of all please try entering recovering mode by pressing Volume Up, Home and Power Button. When you see the samsung boot logo, let go and if you get some options that means you are in recovery.
Click to expand...
Click to collapse
I can only get into download mode. When i try entering recovery mode i get a screen which says firmware upgrade encountered an error an issue. Where do i go from here?
Product code in download mode if blank its SDS .
JJEgan said:
Product code in download mode if blank its SDS .
Click to expand...
Click to collapse
Odin mode
product name: GT-I9300
Custom Binary download: No
current binary: samsung official
System status: custom
John90uk said:
Odin mode
product name: GT-I9300
Custom Binary download: No
current binary: samsung official
System status: custom
Click to expand...
Click to collapse
First of all pls find out which country your samsung is bought from. Europe? usa? Which firmware did you flash with ODIN? Where did you get it from?
May be we can try and root your phone.
haiderijaz said:
First of all pls find out which country your samsung is bought from. Europe? usa? Which firmware did you flash with ODIN? Where did you get it from?
May be we can try and root your phone.
Click to expand...
Click to collapse
It was from the UK. And i have tried to flash a T-mobile Uk firmware as it was on t-mobile. Thanks guys
Recovery mode and rooting are irrelevant to your issue. Try flashing the rescue firmware from the general forum, if that fails then you'll probably need a new motherboard.
Sent from my GT-I9300 using Tapatalk
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
I tried again using I9300XXEMC3 stock rom, but odin 3.04 says
<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> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And fails. My phone says "unsupported dev_type" in red.
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
zhinkk said:
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
TheoDores said:
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
Click to expand...
Click to collapse
I tried following those instructions. I managed to flash the .PIT file. Now I don't see the error message at boot, my screen is just black. BUT I can "sorta" boot into recovery mode (starting recovery message shows for one second, then black screen again). So I'm still stuck.
I can STILL boot into download mode though. And if I try to use CF-Root Odin fails again (same error) and my phone says "unsupported_devtype".
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
JJEgan said:
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
Click to expand...
Click to collapse
Everytime I flash the stock rom odin fails and phone says "unsupported dev_type". In Download mode it says my phone model is T999, but it's actual GT-I9300.
And I don't think I did. I think I had clockwork mod recovery, I'm not too sure though.
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
boomboomer said:
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
Click to expand...
Click to collapse
That really depresses me. Are you sure this is the only solution? Because I remember when my phone WAS working I booted into download mode once and it said the same "T999 Model" and I could still use it. This only happened after I tried flashing the stock i9300 stock rom.
I think it's the cyanogenmod installer that flashed this T999 bootloader for me. When I used the cyanogenmod installer it detected my phone as a AT&T phone and I was dumb enough to click "install" thinking it would work for all galaxy S3's.
I think this guide is exactly what I need (since it restores bootloader), but I can't seem to complete all the steps: http://forum.xda-developers.com/showthread.php?t=2535367
I get to #5 but once I try to install CF-ROOT through odin it says the same unsupported dev type error on my phone.
This is the error I get when trying to use CF-ROOT through Odin3 v1.85:
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
(along with the red "Unsupported dev_type" on my phone in download mode).
I think it was already rooted though, maybe someone could help me reinstall the recovery (cwm) so I can install the bootloader from that guide I just linked?
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Will this delete my EFS? I remember I backed up efs with this guide: http://forum.xda-developers.com/showthread.php?t=1852255
I did: "adb reboot nvbackup"
By restoring to "complete" factory settings, won't this efs be deleted? Can I still backup my efs in my 'soft brick' mode I'm in?
Alright, I've tried using the rescure firmware and all the files, but every time I try I get it a FAIL on odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And my phone says in red "SECURE CHECK FAIL : PIT".
I've spent 12 hours on this now...
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
DualJoe said:
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
Click to expand...
Click to collapse
I tried Kies on two different computers, but whenever I connect my S3 it just says "connecting" forever and never connects to my phone. Tried solutions online, couldn't get it to work.
And I have root access, but can't boot into recovery (says "recovery booting" for a few seconds then goes black screen). So I don't know if I can flash the bootloader manually, unless I did it with odin.
And those seem like busy developers, would they really have time for me? I don't even know what I would ask. :S
Sorry I seem so clueless, I'm just upset/sad/confused/everything right now. Saved up for this phone for a while.
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
DualJoe said:
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
Click to expand...
Click to collapse
Hmm when I had a functional phone it said I had the ZSEMC1 stock rom, so the "bootLoader_ZSEMC1.tar.md5" flashed from odin should work? I got it off this thread: http://forum.xda-developers.com/showthread.php?t=2189063
But I don't know if I'm still on ZSEMC1 since I flashed XXEMC3 with odin (but I think it failed) and I got soft bricked.
What could go wrong? Could I hard brick it by installing that bootloader?
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
DualJoe said:
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
Click to expand...
Click to collapse
I tried the ZSEMC1 and XXEMC3 and XXEMG5 bootloaders from this thread and they didn't work: http://forum.xda-developers.com/showthread.php?t=2189063
(shows unsupported dev type)
How do I get the 'latest' boot loader? That thread is the only one I could really find.
And also I did try installing cwm through odin. It didn't "fail" but it doesn't work when I try to boot into recovery. I'm guessing this has to do with my locked bootloader?
Really don't know what to do at this point. :/
New motherboard if you have tried the fixes .
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
DualJoe said:
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
Click to expand...
Click to collapse
I tried cwm and twrp. They both install successfully on odin but have the same "recovery starting...." message and they don't work. I've tried connecting the USB when it's in this "recovery" mode but my computer doesn't detect it so I can't start up adb and interface with it.
And also, I doubt I'm going to be able to find any in northwest ohio.I wonder if this service is any good?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Looks promising for $50.
Sorry I've been on this problem for so long guys, I'm just stubborn and can't get over the fact that it's a software brick and I need to replace hardware. :/