This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
KizzleKat said:
This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
Click to expand...
Click to collapse
Get the official firmware needed on Sammobile.com, you need an account on there. Don't worry it's free. Flash it as PDA on Odin. Make sure your phone is in download mode (volume up+volume down+power). If it boots, the boot animation might start looping. From theres you can access recovery (volume up+power+home). In recovery you wipe data and wipe cache and select reboot. It should work.
Sent from my GT-I8190N using Tapatalk
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Galaxy_Ace_Love said:
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Click to expand...
Click to collapse
Odin 3.07 supports one file package
Humm...
iamareebjamal said:
Odin 3.07 supports one file package
Click to expand...
Click to collapse
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
KizzleKat said:
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
Click to expand...
Click to collapse
Format the data
Put the pit file and tick Repartition. And then flash with Odin.
And you have to use Cooperve pit, not Totoro, it's for SGY
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
KizzleKat said:
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
Click to expand...
Click to collapse
Follow these Guidehttp://forum.xda-developers.com/showthread.php?t=1840645
Sent from my GT-S5830i using Tapatalk 2
Related
Odin fails with a ROM offical or custom... A Kernal flashes with a pass. Is this bricked? I can enter download mode ok, but not upload to recovery?
The Odin log:
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> boot.bin
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any advice would be greatly recieved!
Thanks
Interesting... When flashing the ROM, do you have a .PIT file + ticked Re-partition in ODIN? If not, try that.
Here's the download for stock firmware, straight from SamFirmware (XXKI3, Open Europe, 2.3.5) : http://hotfile.com/dl/130600047/b70801e/I9100XXKI3.rar.html
Phistachio said:
Interesting... When flashing the ROM, do you have a .PIT file + ticked Re-partition in ODIN? If not, try that.
Click to expand...
Click to collapse
I have found a PIT file ~ u1_02_20110310_emmc_EXT4.pit I don't know where it came from though? it exists in a folder on my desktop where Odin is placed. Do you think that will be safe?
I've never flashed with Re-partition ticked in odin. I've read that is dangerous. Is this defo safe to do?
Thanks
mwatson said:
I have found a PIT file ~ u1_02_20110310_emmc_EXT4.pit I don't know where it came from though? it exists in a folder on my desktop where Odin is placed. Do you think that will be safe?
I've never flashed with Re-partition ticked in odin. I've read that is dangerous. Is this defo safe to do?
Thanks
Click to expand...
Click to collapse
Yes, it is dangerous when you don't know what you're doing. Be VERY careful when around .PITs.
But I have soft bricked my GSII 3 times, and I have flashed KH3 recovery package thrice, WITH the .PIT. The .PIT is just to be as fresh and stock as possible.
Download the package I gave you. But also, what are you trying to flash?
Just to be safe, don't use the .PIT that you "found". The name's the same as in the pack I gave you, but better than than sorry
Phistachio said:
Yes, it is dangerous when you don't know what you're doing. Be VERY careful when around .PITs.
But I have soft bricked my GSII 3 times, and I have flashed KH3 recovery package thrice, WITH the .PIT. The .PIT is just to be as fresh and stock as possible.
Download the package I gave you. But also, what are you trying to flash?
Click to expand...
Click to collapse
I was trying to flash stock
GT-I9100_XEU_I9100XWKF3_I9100XXKE7_I9100XEUKD1.TAR in PDA
I'm just downloading the file you posted. Will this package include the PIT?
Thanks for your help!
mwatson said:
I was trying to flash stock
GT-I9100_XEU_I9100XWKF3_I9100XXKE7_I9100XEUKD1.TAR in PDA
I'm just downloading the file you posted. Will this package include the PIT?
Thanks for your help!
Click to expand...
Click to collapse
Anytime
Yes, it will include the .PIT, aswel as MODEM, CODE and CSC (which should be multi).
Also, just to make sure, uninstall KIES. It may interfere on the flashing process + it's useless
Phistachio said:
Anytime
Yes, it will include the .PIT, aswel as MODEM, CODE and CSC (which should be multi).
Click to expand...
Click to collapse
9 mins to go till the file has downloaded...
So just to be sure i need to flash the PIT, Modem, Code and CSC all together with re-partition ticked?
mwatson said:
9 mins to go till the file has downloaded...
So just to be sure i need to flash the PIT, Modem, Code and CSC all together with re-partition ticked?
Click to expand...
Click to collapse
Yes Do you know where to place each one of them? Let's hope it doesn't end up hard bricked
But before you do ANYTHING, can you go into recovery mode (vol. up+home+power)? If so try to wipe user data and cache.
If that doesn't work, try to normally turn on, and if it bootloops, remove the battery.
PS : I am not liable to any damage that may occur Although I've tested myself and all went OK (With KH3, but it's mainly the same thing )
yeah i know where to put them. I can't enter recovery though. It just loops on boot screen. Will this be a problem if i can't wipe data?
Downloaded file asking for a password?
mwatson said:
yeah i know where to put them. I can't enter recovery though. It just loops on boot screen. Will this be a problem if i can't wipe data?
Click to expand...
Click to collapse
Nope, because the .PIT + Re partition will do the job
ok.. neraly there.. Downloaded file asking for a password?
mwatson said:
ok.. neraly there.. Downloaded file asking for a password?
Click to expand...
Click to collapse
I believe it is samfirmware.com
Good luck!
Bugger failed again!
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100-CSC-MULTI-OXAKI3.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Set PIT file..
<ID:0/017> DO NOT TURN OFF TARGET!!
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this is just good for spare now... or a paperweight!
mwatson said:
Bugger failed again!
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100-CSC-MULTI-OXAKI3.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Set PIT file..
<ID:0/017> DO NOT TURN OFF TARGET!!
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this is just good for spare now... or a paperweight!
Click to expand...
Click to collapse
Now this is weird... I have never seen a flash failed when using a .PIT...
I'm sorry to say this, but I think your GSII is hard bricked... Try to flash another 2 times, the same thing.
What it seems is that the NAND got corrupted somehow... And isn't letting ODIN flash properly...
Just tried another couple of times and still no good.
Obrigado pela vossa ajuda. Feliz Ano Novo!
mwatson said:
Just tried another couple of times and still no good.
Obrigado pela vossa ajuda. Feliz Ano Novo!
Click to expand...
Click to collapse
The last thing that comes to mind is... To flash a stock kernel (preferably KI3 Stock Kernel) from Intratech's thread. If successful, flash the the recovery package again. If unsuccessful, as a last resort, flash the old bootloader provided in his thread aswell (follow his instructions!), and if successful, flash the KI3 package I gave you again. That may screw up the GSII's mind and make it work
As it is unfortunately hard bricked, I'm giving out all options that come to my mind
De nada ! I wish you a joyful new year aswell
In a less confusing manner :
1. Flash KI3 Stock Kernel from Intratech'a thread.
2. Flash Recovery package
3. If recovery package is not flashed, re flash the stock kernel
4. Flash old bootloader provided in the same thread
5. If it boots, then yay. If not :
6. Re flash the recovery package.
With that "guide", I want to exploit the fact that you can root a kernel, so if you root a stock kernel, you get lucky...
Also, are you sure you put the stuff in the right place? .PIT -> PIT, Code -> PDA, Modem -> Phone, CSC -> CSC and ticked Re-partition, Auto Reset and F.Timer reset (irst 3)
Yep.. thats what i did.. Screen shot for you in case you can spot anything? Defo kies not running as you can see from the screen shot.
The phone still goes into download mode though?
Use a different USB port on your PC. Try to use one of the Ports on the rear of your case and not the ones on the front or top of the case.
Sleepycat3 said:
Use a different USB port on your PC. Try to use one of the Ports on the rear of your case and not the ones on the front or top of the case.
Click to expand...
Click to collapse
Tried different ports. Still no luck.. During the flash process is tries to boot the goes to fail.
It not like i can send this back as it has a count of 7 custom downloads.
thanks
<ID:0/040> Removed!!
<ID:0/040> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> APBOOT_I9100GZCKH4_CL484595_REVr07_user_low_ship.t ar.md5 is valid.
<OSM> CODE_I9100GZCKH4_CL484595_REVr07_user_low_ship.tar .md5 is valid.
<OSM> MODEM_I9100GZCKH4_REV_00_CL1050825.tar.md5 is valid.
<OSM> GT-I9100G-CSC-MULTI-OZHKH4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/040> Odin v.3 engine (ID:40)..
<ID:0/040> File analysis..
<ID:0/040> SetupConnection..
<ID:0/040> Initialzation..
<ID:0/040> Set PIT file..
<ID:0/040> DO NOT TURN OFF TARGET!!
<ID:0/040> Get PIT for mapping..
<ID:0/040> Firmware update start..
<ID:0/040> MLO
<ID:0/040> NAND Write Start!!
<ID:0/040>
<ID:0/040> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any solution ?
hey quickgsm
are you using a Chinese version of i9100g.because flashing chinese firmware with odin will only work for chinese i9100g not i9100g of any other country.post details about your i9100g.
darkshadow1997 said:
hey quickgsm
are you using a Chinese version of i9100g.because flashing chinese firmware with odin will only work for chinese i9100g not i9100g of any other country.post details about your i9100g.
Click to expand...
Click to collapse
i try to flash by many firmware if i use I9100GXXLPN_I9100GXEFLPN_XEF_2 or I9100GXXLPN_XEFLPN_France_Android_4.0.3 flash working 100% but phone stuck on samsung logo and if i use this firmware I9100GZCKH4 i jet error :
<ID:0/040> Firmware update start..
<ID:0/040> MLO
<ID:0/040> NAND Write Start!!
<ID:0/040>
<ID:0/040> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PS : my I9100G from france
why did you tick repartition for? un-tick taht option
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
omg why did you tick all????
only tick PDA file and put in the firmware
ad_ek said:
why did you tick repartition for? un-tick taht option
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
omg why did you tick all????
only tick PDA file and put in the firmware
Click to expand...
Click to collapse
same issue if i don't tick repartition
quickgsm said:
same issue if i don't tick repartition
Click to expand...
Click to collapse
only tick the pda
nothing else
n try to flash a gb firmware firstly and thn try to flash ics
Devices-
Samsung galaxy s2 i9100g (Cm9-Nightly build)
sony walkman 8 ( Cm9 Stable )
Blackberry 9300 cracked for bbm
Press thnks if i tried to help
im not sure which guide you are following. but the normal procedure to flash firmware with odin is only using ODIN is to only tick the PDA option. and insert the firmware file which you have downloaded.. im trying to
help you ...but if you are getting mad...its ok. you can find your way.
ad_ek said:
im not sure which guide you are following. but the normal procedure to flash firmware with odin is only using ODIN is to only tick the PDA option. and insert the firmware file which you have downloaded.. im trying to
help you ...but if you are getting mad...its ok. you can find your way.
Click to expand...
Click to collapse
yup your right ad_ek ..just use the pda option and dont touch other thing...can your phone boot to eg: recovery or download mode?use pit only when your phone is in soft brick state..if fail again try reboot your pc/change usb port and try again
Wonder why OP tick so many for what. Just tick PDA.. that it. Don't touch other things.
PIT only required if your phone is softbrick.
Chinese ROM
Looks like you have a Chinese phone with the locked bootloader, go back to stock for now.
-delete-
In my case it is only one file .tar.md5 can fix soft brick ?!!
i think it's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't work , but a 3 file can fix soft brick
i am not able to go to recovery mood ! phone show Samsung galaxy S2 GT-I9100G
quickgsm said:
In my case it is only one file .tar.md5 can fix soft brick ?!!
i think it's better to flash a 3 part, since sometimes in a soft brick, a single files doesn't work , but a 3 file can fix soft brick
Click to expand...
Click to collapse
Sorry, but just flash the tar.md5 file as pda in odin. I really suggest not to think but to follow the instructions given.
quickgsm said:
i am not able to go to recovery mood ! phone show Samsung galaxy S2 GT-I9100G
Click to expand...
Click to collapse
Try to find the stock kernel for the chinese ICS...last time i had this situation i was able to flash the kernel even i could not get in download mode.
Don't panic. I am sure that the ppl around will help you so that you don't come out with an expensive paperweight
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLPN_I9100GXXLPN_I9100GXEFLPN_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> MLO
<ID:0/010> NAND Write Start!!
<ID:0/010> Sbl.bin
<ID:0/010> param.lfs
<ID:0/010> factoryfs.img
<ID:0/010> zImage
<ID:0/010> modem.bin
<ID:0/010> cache.img
<ID:0/010> hidden.img
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/010> Removed!!
phone still show Samsung galaxy S2 GT-I9100G can help me to fix it ?
Which is your problem right now?
Yesterday I was flashing with Odin v1.85 and it was a total mess. I had NAND Write error like you had. I downloaded Odin v1.7 and I got my S2 back alive.
But with your last log, it flashed, so I don't understand what's your problem. Doesn't boot?
antonio1475 said:
Which is your problem right now?
Yesterday I was flashing with Odin v1.85 and it was a total mess. I had NAND Write error like you had. I downloaded Odin v1.7 and I got my S2 back alive.
But with your last log, it flashed, so I don't understand what's your problem. Doesn't boot?
Click to expand...
Click to collapse
i am not able to go to recovery mood ! phone show Samsung galaxy S2 GT-I9100G
quickgsm said:
i am not able to go to recovery mood ! phone show Samsung galaxy S2 GT-I9100G
Click to expand...
Click to collapse
It just keeps in the first boot screen with/without a yellow triangle and the name Samsung and the model in white letters?
Please be a little more clear and descriptive so we can be sure what you are talking about
my problem :
the phone got stuck at boot up screen after the update showing the message Samsung Galaxy S2 GT-I9100G. Please provide the solution for this.
quickgsm said:
my problem :
the phone got stuck at boot up screen after the update showing the message Samsung Galaxy S2 GT-I9100G. Please provide the solution for this.
Click to expand...
Click to collapse
OK. So download a stock firmware for your model, which I guess you already have by the first post, and download Odin v1.7 (http://www.mediafire.com/?jyyux6yxem8uojn).
Use Odin v1.7 to flash just PDA (the CODE file). If doesn't boot (if it says error flashing let me know), try changing USB port (remember to reboot the device in download mode each time you want to flash with Odin).
If not, add the other files but without PIT. Finally if it doesn't boot, try with PIT too.
Let me know your progress. Best luck
I have a bricked i9300 galaxy s3 16gb,i have it bricked 3 months or more...i want to resurrect it, but i dont know how... Please, help, I had flashed every kind of roms but it doesn´t starts,it continuously reboot in the samsung screen,i delete ALL in the odin but without any success... Please help me, i am not a developer,I am a spanish 18 years old and I am very lost...please help...
I tryed to flash the stock rom of samsung
I9300XXELLC
I tryed to flash the "unbrick" method of the 2nac program but it fails when it starts to flash (it fails when he beggins to flash "boot.img")
http://www.2nas.com/index.php/site/page?view=howto#unbrick
I tryed to flash the resurrect rom to unbrick it
http://checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
And all this methods of unbrick failed. Now, I am trying to flash this
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
This is the message of odin when I flash the files
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<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)
I don´t know why it fails, because when i flash only a PDA file,the stock rom for example,it flash perfectly, but when I flash other files it fails.
Somebody can help me??? PLEASE...
you should flash a stock FW via odin.
just make sure before starting odin you need to close all kies processes via task manager, this could lead to the failed operation.
GL
i tried it but it fails... :S
eytan123 said:
you should flash a stock FW via odin.
just make sure before starting odin you need to close all kies processes via task manager, this could lead to the failed operation.
GL
Click to expand...
Click to collapse
when i flash it,the process is success but after the flash,when I try to turn the device on just restarts over and over again when it reaches the samsung screen, the animated image, not the "samsung galaxy s3" beggining image
Go into recovery and do a reset after the flash
1) Flash a stock ROM via ODIN
2) If it keeps restarting at the Samsung logo, go into recovery (turn the phone off and then hold volume up + home button + power button until the Android appears) and factory reset/wipe data.
3) Restart
DeadSOL said:
1) Flash a stock ROM via ODIN
2) If it keeps restarting at the Samsung logo, go into recovery (turn the phone off and then hold volume up + home button + power button until the Android appears) and factory reset/wipe data.
3) Restart
Click to expand...
Click to collapse
after the flash i cant enter to recovery mode...
davidmartins said:
after the flash i cant enter to recovery mode...
Click to expand...
Click to collapse
You will need to flash 3 things
1. Stock firmware
2. Cf auto root
3. CWM recovery touch
And then enter into recovery and make a reser
Sent from my GT-I9300
Recovering a bricked Galaxy S3
davidmartins said:
I have a bricked i9300 galaxy s3 16gb,i have it bricked 3 months or more...i want to resurrect it, but i dont know how... Please, help, I had flashed every kind of roms but it doesn´t starts,it continuously reboot in the samsung screen,i delete ALL in the odin but without any success... Please help me, i am not a developer,I am a spanish 18 years old and I am very lost...please help...
I tryed to flash the stock rom of samsung
I9300XXELLC
I tryed to flash the "unbrick" method of the 2nac program but it fails when it starts to flash (it fails when he beggins to flash "boot.img")
http://www.2nas.com/index.php/site/page?view=howto#unbrick
I tryed to flash the resurrect rom to unbrick it
http://checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
And all this methods of unbrick failed. Now, I am trying to flash this
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
This is the message of odin when I flash the files
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<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)
I don´t know why it fails, because when i flash only a PDA file,the stock rom for example,it flash perfectly, but when I flash other files it fails.
Somebody can help me??? PLEASE...
Click to expand...
Click to collapse
I've got a Galaxy S3 which goes into a reboot loop from time to time and I found this which should help you:
http://reviews.cnet.co.uk/mobile-phones/how-to-recover-a-bricked-samsung-galaxy-s3-50009490/
I'd be interested to know if it solves your problem.
JohnOfStony said:
I've got a Galaxy S3 which goes into a reboot loop from time to time and I found this which should help you:
http://reviews.cnet.co.uk/mobile-phones/how-to-recover-a-bricked-samsung-galaxy-s3-50009490/
I'd be interested to know if it solves your problem.
Click to expand...
Click to collapse
Sorry but...I´ve done it and it reboots like before... Really thank you even so...
Problem...
I think i fried the EMMC... because when i try to flash the pit it doesn´t works...
But when I try to flash a PDA file, the stock rom, it flash succesly, but after the flash, it reboots continuously... i think the partition of bootloader is the bad flashed here...
If you´ve got other pit files can you post here the url? Thanks!
davidmartins said:
I think i fried the EMMC... because when i try to flash the pit it doesn´t works...
But when I try to flash a PDA file, the stock rom, it flash succesly, but after the flash, it reboots continuously... i think the partition of bootloader is the bad flashed here...
If you´ve got other pit files can you post here the url? Thanks!
Click to expand...
Click to collapse
When stock rom has flashed by odin each write is verified and if any error is found will be logged in odin textarea.
So, probably problem is not emmc.
The common cause to boot loop is data partition has been corrupted.
To solve is necessary format data partition.
To boot direct in recovery mode, use the combination volume_up+home+power.
Use recovery menu to issue the factory reset.
davidmartins said:
I have a bricked i9300 galaxy s3 16gb,i have it bricked 3 months or more...i want to resurrect it, but i dont know how... Please, help, I had flashed every kind of roms but it doesn´t starts,it continuously reboot in the samsung screen,i delete ALL in the odin but without any success... Please help me, i am not a developer,I am a spanish 18 years old and I am very lost...please help...
I tryed to flash the stock rom of samsung
I9300XXELLC
I tryed to flash the "unbrick" method of the 2nac program but it fails when it starts to flash (it fails when he beggins to flash "boot.img")
http://www.2nas.com/index.php/site/page?view=howto#unbrick
I tryed to flash the resurrect rom to unbrick it
http://checkrom.com/threads/resurrection-odin-checkrom-evohd™-v4.896/
And all this methods of unbrick failed. Now, I am trying to flash this
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
This is the message of odin when I flash the files
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXDLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXDLID_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_BTU_I9300OXADLJ4_368423_MULTI_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<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)
I don´t know why it fails, because when i flash only a PDA file,the stock rom for example,it flash perfectly, but when I flash other files it fails.
Somebody can help me??? PLEASE...
Click to expand...
Click to collapse
Dear Brother I think u flash stock recovery 1st and then try to flash new rom.then f-reset and restart,mey bit solve.sorry 4 my bad English.find zip 4 sotck recovery
sam77744 said:
Dear Brother I think u flash stock recovery 1st and then try to flash new rom.then f-reset and restart,mey bit solve.sorry 4 my bad English.find zip 4 sotck recovery
Click to expand...
Click to collapse
flash via odin
I've tried same as davidmartins but all failed w/ the same Odin log.
Initial rom on my S3 was I9300XXLEF (Hong Kong) and I flashed Samsung Galaxy S III GT-I9300 Stock Firmware Collection I9300XXEMA2 after that it didn’t re-boot because of wrong ROM, if I try to get into recovery it shows the “Firmware upgrade encountered issue. Please select recovery mode in Kies & try again” screen.
I tried also to re-flash the Stock FW but failed too.
Any further advise to bring my S III back to life would be highly appreciated.
Cheers.....LinChina
your motherboard are dead .. I had the same problem with an HTC HD2. motherboard has failed without doing something wrong.
andreivibefm said:
your motherboard are dead .. I had the same problem with an HTC HD2. motherboard has failed without doing something wrong.
Click to expand...
Click to collapse
i will do a JTAG in a week.If it doesn´t works, I will buy another galaxy s3 T.T
davidmartins said:
i will do a JTAG in a week.If it doesn´t works, I will buy another galaxy s3 T.T
Click to expand...
Click to collapse
y havet same isuse bat y resolvet . try to flash diferent cw recovery and then the room
sory for bad eng.
hey,
so my friend brought me his S3, never rooted or tampered with. He just said the phone went into boot and never recovered. I can go in download mode but not recovery (my initial plan was to wipe cache).
he would kind of want his data intact but I don't know how viable that is by now..
Any advice?
Thank you
Posklapenzi said:
hey,
so my friend brought me his S3, never rooted or tampered with. He just said the phone went into boot and never recovered. I can go in download mode but not recovery (my initial plan was to wipe cache).
he would kind of want his data intact but I don't know how viable that is by now..
Any advice?
Thank you
Click to expand...
Click to collapse
Try flashing a custom recovery like twrp or philz touch. But it actually sounds like a soft brick. worst case scenario you would have to flash a new firmware/
this is the last one http://forum.xda-developers.com/showthread.php?t=1835931
Posklapenzi said:
hey,
so my friend brought me his S3, never rooted or tampered with. He just said the phone went into boot and never recovered. I can go in download mode but not recovery (my initial plan was to wipe cache).
he would kind of want his data intact but I don't know how viable that is by now..
Any advice?
Thank you
Click to expand...
Click to collapse
The phone's own recovery mode is not much flexible as other third-part recoveries. So I guess you have to install CWM recovery and wipe dalvik cache from there before booting. Try installing CWM recovery via Odin and then wipe dalvik cache. And don't worry, installing custom recovery won't root your phone.
If the stock recovery can, wipe the cache and dalvik cache
Sent from my GT-I9300 using Tapatalk
It appears I can't flash any recovery:
<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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Report from Odin. Could I flash a stock firmware tho?
Can't mount stock rom either. I tried ticking repartition too, this is what comes out:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMG4_I9300DBTEMG3_I9300XXEMG4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
Bump.. Please help someone.
Make sure you have the latest odin and the correct drivers and also make sure kies is not open
Sent from my SAMSUNG GT-N7105 using XDA Premium 4 mobile app
Posklapenzi said:
It appears I can't flash any recovery:
<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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Report from Odin. Could I flash a stock firmware tho?
Click to expand...
Click to collapse
Try to flash PIT partition via odin( be careful you must have the PIT file sweatable for your model )
abidifethi said:
Try to flash PIT partition via odin( be careful you must have the PIT file sweatable for your model )
Click to expand...
Click to collapse
How can I know what that is? I can't boot the phone to see the exact model? Says I9300GSMH on the back behind the battery so I should assume that's accurate?
Posklapenzi said:
How can I know what that is? I can't boot the phone to see the exact model? Says I9300GSMH on the back behind the battery so I should assume that's accurate?
Click to expand...
Click to collapse
http://widefide.com/mobile/galaxy-s3-boot-problem-solution
I am trying to flash phone back to stock ROM due to my phone only booting in Odin mode, but I keep getting FAIL! flash attempts in Odin. The failure occurs at the message line FAIL! (Auth). I have tried flashing VRUAMDK_NoWipe.tar and CF-Auto-Root-jflte-jfltexx-gti9505.
Portisface said:
I am trying to flash phone back to stock ROM due to my phone only booting in Odin mode, but I keep getting FAIL! flash attempts in Odin. The failure occurs at the message line FAIL! (Auth). I have tried flashing VRUAMDK_NoWipe.tar and CF-Auto-Root-jflte-jfltexx-gti9505.
Click to expand...
Click to collapse
Were you originally on MDK? If so, have you checked MD5?
riker147 said:
Were you originally on MDK? If so, have you checked MD5?
Click to expand...
Click to collapse
Sorry the full filename is VRUAMDK_NoWipe.tar.md5. Is that what you're talking about?
Portisface said:
Sorry the full filename is VRUAMDK_NoWipe.tar.md5. Is that what you're talking about?
Click to expand...
Click to collapse
No. What build were you on before your problems?
riker147 said:
No. What build were you on before your problems?
Click to expand...
Click to collapse
I don't remember other than I was at 4.3. I had my phone rooted using SuperSU and I tried unrooting so I could download the latest OTA. I was still getting errors to install updates after disabling SuperSU and was getting sick of my phone constantly trying to update so I decided to try to revert back to stock. I downloaded Odin and the TAR file I mentioned and followed the instructions to restore back to stock ROM. I received that error and found in another forum that someone got it to work using CF-Auto-Root-jflte-jfltexx-gti9505. I tried that to and same issue. I can't find any other solutions.
Portisface said:
I don't remember other than I was at 4.3. I had my phone rooted using SuperSU and I tried unrooting so I could download the latest OTA. I was still getting errors to install updates after disabling SuperSU and was getting sick of my phone constantly trying to update so I decided to try to revert back to stock. I downloaded Odin and the TAR file I mentioned and followed the instructions to restore back to stock ROM. I received that error and found in another forum that someone got it to work using CF-Auto-Root-jflte-jfltexx-gti9505. I tried that to and same issue. I can't find any other solutions.
Click to expand...
Click to collapse
You need to find what build you were on because you can't flash an older build. You can only flash your original build or newer. If you want the latest OTA, (Kit Kat), you need to download the .tar file for that.
riker147 said:
You need to find what build you were on because you can't flash an older build. You can only flash your original build or newer. If you want the latest OTA, (Kit Kat), you need to download the .tar file for that.
Click to expand...
Click to collapse
I am currently downloading Kit Kat. However, I was trying to flash it one more time to copy and paste the message lines here and now the error is "There is no PIT partition." I have already downloaded the PIT for my phone. I am I gonna have to use that now?
Portisface said:
I am currently downloading Kit Kat. However, I was trying to flash it one more time to copy and paste the message lines here and now the error is "There is no PIT partition." I have already downloaded the PIT for my phone. I am I gonna have to use that now?
Click to expand...
Click to collapse
I think you might me be over complicating things. If you're going with NC5 (Kit Kat) and you can use Odin, I think all you're going to need is the .tar file.
riker147 said:
I think you might me be over complicating things. If you're going with NC5 (Kit Kat) and you can use Odin, I think all you're going to need is the .tar file.
Click to expand...
Click to collapse
So the "no PIT partition" message isn't a problem?
Hi,
I've been trying to revert to stock rom just like the OP. As you'll see my adventure ends at aboot.mbn. I downloaded the latest build (SCH-I545_MDK_562219_Stock_Restore.tar.md5) according the tutorial I'm using. I'm using the latest version of Odin3 1.85 (also according to the tutorial. Also, I'm using the Samsung Galaxy S4 VZW (SCH-1545) phone. Any and all help will be appreciated!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gotshot87 said:
Hi,
I've been trying to revert to stock rom just like the OP. As you'll see my adventure ends at aboot.mbn. I downloaded the latest build (SCH-I545_MDK_562219_Stock_Restore.tar.md5) according the tutorial I'm using. I'm using the latest version of Odin3 1.85 (also according to the tutorial. Also, I'm using the Samsung Galaxy S4 VZW (SCH-1545) phone. Any and all help will be appreciated!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi guys,
1st thing thank you for the informations and knowledge i have learned here at XDA.
I have the same problem . I have done all i believe i can from all the research i have done and come acrossed. Hands up in the air and i surrender.
Need some help
If anybody could please fhank you so much...
It looks like you are trying to unlock the wrong baseband version.
The only Verizon Samsung Galaxy S4 (SCH-I545), aka jfltevzw, that has an unlockable bootloader is the one that has the baseband version "I545VRUAMDK".
And once the baseband is updated to a newer one, it cannot be downgraded.
Sent from my SCH-I535 using XDA Free mobile app