hello guys im fernando im new to the forum, i would like to get some help with my little problem with my s3... im very sorry about my english spelling...
the problem is that i flashed a custom rom into my phone.. it worked great for the last 5 months or so.... in the past month i installed cyanogenmod 10.1... it was great.. but i have a little situation and i have to sell my s3 (no worries, im getting a new one hehe) but the buyer wants to get the phone with stock samung official rom... i downloaded the lastest official rom but i dont know how to install it and leave the phone like out of the box like new.... can someone help me with the steps on how to get to sotck premium suite samsung official rom from cyanogenmod 10.1??? thank you in advance guys
Hi Fernando.
You should read the basics, how to flash stock ROMs via Odin, there's loads of useful information on here if you look for it. And don't forget to do a factory reset
Glebun said:
Hi Fernando.
You should read the basics, how to flash stock ROMs via Odin, there's loads of useful information on here if you look for it. And don't forget to do a factory reset
Click to expand...
Click to collapse
thanks a lot glebun for your asnwer, but the question is.. i can flash the stock rom with odin normally?.. doesnt matter if i had a previous custom rom and cm10.1?'
No, it doesn't matter, as long as you do a factory reset from recovery right afterwards. Also, they may want to have the flash counter at zero, it can be easily reset, all the info is there for you to read
Glebun said:
No, it doesn't matter, as long as you do a factory reset from recovery right afterwards. Also, they may want to have the flash counter at zero, it can be easily reset, all the info is there for you to read
Click to expand...
Click to collapse
sorry bro me again.. i tried to flash my phone with odin used the .md5 of stock rom plugged the phone everything nice... after a min or so it says fail!... heres the log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELLC_I9300PHEELL3_I9300XXELLA_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> system.img
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
make sure Kies is not running
it worked but....
ty for your ansers and patience... i load the stock rom with odin all went fine but now went it turned on just stays in th samsung logo and keeps repeating the boot samsun image over and over... now i realy dont know what to do help please
flashing rom 101: just flash it like every other rom. put the stock rom on your phone. reboot to cwm recovery. do wipe cache/ wipe davilk cache/ wipe user data-factory reset then flash zip from sd card. look for the rom .zip and flash it.
edit: take the battery out of the phone. put it back in. shoot i just read its stuck on boot loop. yea i dont know. im a noob at that part. well search around the forums or use google.
also maybe look here: http://forum.xda-developers.com/showthread.php?t=2111641
Go into recovery, wipe data and cache.
ty guys but the problem is that when i flashed the custom it doesnt come with CMW so i cant get into recovery to flash a custom or something
just do a factory reset from recovery
Related
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.
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
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 everyone,
I tried updating my Verizon Galaxy S4 to Lollipop via Samsung Kies. The update process produced an error message (at app. 10%) and offered me to start the recovery process, which failed subsequently. Needless to say, Android OS does not work, however I can still boot into download/recovery mode.
I've been trying to flash various stock ROMs via Odin 3.10 with no success. The build numbers of the ROMs I've been trying to flash contained the I545VRUFNC5 number, since I tried preserving compatibility with the previous (Stock) ROM that had the same build number. Prior to flashing Lollipop via Kies, I made the made a screenshot (attached below) in case I ran into some kind of trouble. It contains the Model/Build of my S4.
I've also tried using a PIT file during the flashing process with no success.
The error message Odin gives me always reads:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNC5_I545VZWFNC5_I545VRUFNC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The main question is whether I need to stick to build I545VRUFNC5 to reflash. If not, which Stock ROM am I able to Install via Odin without bricking the phone further
For exact phone model/specs pls open the screenshot below. I would also be very grateful if someone could provide me a stock ROM (name/link/version) that I could flash via Odin to resolve the mess Kies and I created.
Any help is much appreciated.
Thanks in advance.
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
XxD34THxX said:
Make sure to get FULL WIPE AND REPARTITION. All data will be lost..
Click to expand...
Click to collapse
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
intel.fan said:
Thanks for the reply. Sadly, I don't have a custom recovery flashed on my phone. I already tried flashing TWRP and the process resulted in a similar error message as described above (auth fail/error). I've already performed a factory reset via the stock recovery, so the data is already gone
Click to expand...
Click to collapse
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
XxD34THxX said:
Bad mistake to do TWRP. With reading, you would have known that TWRP is restricted to MDK... Safestrap(@hashcode) is what you have to use. Or Flashfire(@chainfire) or the New Multisystem tool by @hsbadr... Use Odin, get the zip, and flash it in the PDA( or AP) slot. I fixed my friend's when he did that, but he got lucky...
Click to expand...
Click to collapse
No mate, since the bootloader seems to be locked. It simply didn't flash TWRP - the stock bootloader is still present and running. Trying to flash TWRP was kind of a desparate measure, since I don't have OS access to flash/install any of the above. Also, my phone was 100% stock Kitkat 4.4.2 with no root access
Resolved the issue! =)
The problem was in that the Lollipop update process had already been started (unsuccessfully), Odin was "seeing" the flash process as a downgrade - so it wouldn't allow it.
I tried flashing a stock Lollipop ROM via Odin and it worked like a charm
Thanks for your support.
@mods: Please close/archive this thread.
I tried to unroot my T-Mobile Galaxy S6. I tried to go the easy route and just unroot through SuperSU. As soon as I did that, it went straight into a boot loop. I immediately loaded it into the recovery mode to wipe data/factory reset the phone and to wipe the cache partition. That did no good either. I then tried to flash the stock T-Mobile S6 firmware(5.0.2) onto it. Alas, that fails too. Fails at NAND Write Start. When I was rooting, I had this same issue but I can't remember what I did to fix that issue.
Here's the full log: <ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I would greatly appreciate any assistance on my issue.
Thanks,
Steven
Your device partition might be formatted in someother format. Which version of supersu did u use for rooting? System mode or systemless? Did u do any modifications to the file system, like uninstalling any system app? Are u able to boot into recovery? If so stock recovery or custom recovery?
KingWilliams said:
Your device partition might be formatted in someother format. Which version of supersu did u use for rooting? System mode or systemless? Did u do any modifications to the file system, like uninstalling any system app? Are u able to boot into recovery? If so stock recovery or custom recovery?
Click to expand...
Click to collapse
I have no idea what version of SuperSU I used and if it was system mode or systemless. I didn't do any modifications to my file system. Yes, I can boot into recovery. (I think its stock??)
Sorry, I am pretty new to this.
If it's failing at sboot.bin, then that usually means you are trying to install a version that is older than the one currently installed. Reboot to recovery (I'm assuming you're still on the stock one...?) and check the version there and then download / install that one. If you have a custom recovery, then just download the newest one you can find and should be fine.
es0tericcha0s said:
If it's failing at sboot.bin, then that usually means you are trying to install a version that is older than the one currently installed. Reboot to recovery (I'm assuming you're still on the stock one...?) and check the version there and then download / install that one. If you have a custom recovery, then just download the newest one you can find and should be fine.
Click to expand...
Click to collapse
That makes sense! I was going to try that. But, I didn't have enough time to try it before I had to go to sleep. I will try that as soon as I get home. My friend says that I also need to install TWRP in order to flash my phone. Is that correct?
misfitmatter said:
That makes sense! I was going to try that. But, I didn't have enough time to try it before I had to go to sleep. I will try that as soon as I get home. My friend says that I also need to install TWRP in order to flash my phone. Is that correct?
Click to expand...
Click to collapse
TWRP is a custom recovery thats required only when u want to flash custom zip files like custom roms, kernels, mods etc...it has no connection with flashing a firmware