Hello guys!
I am new here, nice to meet all you guys. I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
trufogio said:
Hello guys!
I am new here, nice to meet all you guys.
Spoiler
I have a huge problem with my S3 and I hope it can be fixed without having to replace the motherboard. Last week a flashed the 24th December nightly of CM14. I did a clean flash through my recovery (TWRP) and everything was working fine until two days ago when I found my phone stuck with the CM logo. I removed the battery and tried to switch it on again after reinserting it: it only showed the "Galaxy SIII" logo and couldn't boot. Now, my phone is still in this state. I can go into download mode (and it correctly shows the model number) and I have full access to the twrp recovery. However, the recovery says "no OS installed" and shows an internal memory of 0mb. It is impossible to do a full wipe as it can't mount any partition (only the recovery partition). Using Odin, I can't flash ANY rom I tried so far... I think it's a soft break as I have full access to the recovery, with a full funcioning touch screen and vibration. Is there a way to fix it? Any help? When I'm home I will give you more details and even post some photos of the error messages I get from Odin and the recovery.
Happy new year to everyone and thanks for your help.
Click to expand...
Click to collapse
You should try to flash a Factory formatting firmware and remapping the partitions with Pit file using Odin. If this doesn't work... There's nothing else to do
TapaStalking
Where can I find the right factory formatting firmware and pit file? I have an International version of GSIII bought in Italy (16gb). In case it doesn't work, will replacing the motherboard do the job? The thing I still don't get is how can the internal memory be damaged if I have full access to the recovery? The recovery is stored in the internal memory, isn't it?
Are you Italian? If so, take a look at this... http://www.androidiani.com/forum/showthread.php?t=344896
TapaStalking
Yes, I am! Thanks, I'll have a look at that link.
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<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.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
西村大一 said:
EMMC brick bug claims another device. Nothing can be done other than replacing the EMMC chip in a specialised repair shop. Or buy another motherboard (i know you're against it, but sh*t happens, yo).
Click to expand...
Click to collapse
But if the EMMC chip is bricked, how can I still enter into recovery mode? Isn't the recovery stored in the EMMC like any other partition? Am I missing something? I mean, If I couldn't go into recovery I would agree with you, the EMMC would have broken. But as I DO enter into recovery (and can read some files) looks like another problem... If I am wrong, please explain how it works because I'm a little bit lost
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
trufogio said:
Ok, I've tried flashing a PIT file to repartition through Odin and this is what I got:
<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.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
When I switch it on I can still go in download mode and recovery, but nothing has changed. I will try now to download a factory formatting firmware.
Click to expand...
Click to collapse
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
ivano949 said:
Why "added" come later then repatriation operation... I think you should try and try.... Maybe you can change Odin version too. Don't give up just after one try
TapaStalking
Click to expand...
Click to collapse
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
trufogio said:
Thanks, I will try!! Anyway if it keeps failing, I found a new gs3 motherboard for just 20 euros...if it's not too difficult to replace I think I will buy it.
Click to expand...
Click to collapse
That's difficult for nothing. Done this summer on my sweet S3, there are tons of tutorial in youtube.... The only thing is wishing new motherboard is OK and don't have a locked imei.... Think at this... Maybe is just time to have a new (and newer) phone
TapaStalking
Are you using the original Samsung USB cable and USB 2.0 ports?
audit13 said:
Are you using the original Samsung USB cable and USB 2.0 ports?
Click to expand...
Click to collapse
yes, I am! I tried several times but it fails every single time... I think I'll buy a new motherboard, 20 euros is a great price. I already have a newer phone (galaxy s6) but I need this s3 to be back to work in order to use it with my secondary sim card Anyway, If you think about installing CM14 nightlies, they are not stable at all at the moment.
trufogio said:
I had researched before posting and hadn't found anything helpful, that's why I asked here. There is no need to be rude as this forum is here to offer help between all members of the community
Click to expand...
Click to collapse
I am not intending to be rude, I even explained what EMMC Brick bug means as a way to educate you and the ones that search the forums for explanations, but since you got my post deleted because you thought i was trying to be rude, well yeah, okay. That's why I hate people.
Please keep it respectful in here, and respect each others opinions..
Here's a thorough read for you guys : XDA Rulesforum.xda-developers.com/announcement.php?a=81
Regards
Vatsal,
Forum Moderator.
Related
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Sbl.bin
I flashed rom through Odin and its return is like this.
The Sbl.bin is likely to be related to the bootloader.
I cannot access to the recovery or normally reboot.
What can I do?? I tried flashing for several times.
Zillions of thanks if you guys can help me!!!!
What is your device?
aceofclubs said:
What is your device?
Click to expand...
Click to collapse
i9100 of course.
superfan' said:
i9100 of course.
Click to expand...
Click to collapse
Why did you start a new thread? You already had a perfectly good thread going for the same problem here: http://forum.xda-developers.com/showthread.php?p=24175814.
And you've apparently decided to ignore all the advice in that thread that said to flash back to a stock GINGERBREAD firmware, since you again are trying to flash LPQ, which is one of the earlier ICS releases.
superfan' said:
i9100 of course.
Click to expand...
Click to collapse
Not of course. Because the problem you describe is what happens when you try to flash I9100 firmware on a model like I9100G or others that are called SGS2 but are different hardware. Only true way to tell is read the sticker under the battery.
Anyway forget this thread and take the advice in the other thread and report back there.
Good luck.
ctomgee said:
Why did you start a new thread? You already had a perfectly good thread going for the same problem here: http://forum.xda-developers.com/showthread.php?p=24175814.
And you've apparently decided to ignore all the advice in that thread that said to flash back to a stock GINGERBREAD firmware, since you again are trying to flash LPQ, which is one of the earlier ICS releases.
Click to expand...
Click to collapse
I tried to flash KI3, the gingerbread, it still fails. I think it is a new problem, and it is related to the NAND rw corruption mentioned by others. Therefore, I started a new post but not ignoring others' advice.
If you can help me with my problem, zillions of thanks then.
Flash a stock GB rom and see what happens .
jje
Given you say you've tried everything suggested, and given you think it's a bootloader issue, there are literally dozens and dozens of posts on here about same.
Do a Google search (rather than using XDA search), and append 'XDA' to whatever your search terms are.
This problem you're having is not common, and you're not going to find a fix easily for this (as you're discovering) short of having it JTAG'd or sending it to a Samsung service center.
Is samsung customer service accepted to handle this, even i have some custom binary no?
Or if i pay some money, they wll fix that for me??
Sent from my GT-P7500 using XDA
Yep. They'll fix it, but you'll more than likely end up paying for it. A JTAG repair might be a cheaper option. Here's one in the US, I'm sure there are many others around the world (maybe near you, search Google).
Can you still enter download-mode (Vol. down + Home Button + Power Button)? If so, you can try these steps in this Guide here
Be careful with Re-Partition..i ruined my device some days ago with it after try to fix nand rw corruption.
I have tried all of those before. But i even can't flash things through. Even vthe kernel, recovery and bootloaders.
Sent from my GT-P7500 using XDA
So when you try to flash a 3-Part Firmware (without Re-Partition) it stucked again?
PS: Be very careful .. I has a very similar problem and with Re-Partition I shoot it up -.- (http://forum.xda-developers.com/showthread.php?p=24115788#post24115788)
What have you done to shoot it up??
I stucked even i flashed a three part firware without repartition and pit file
Sent from my GT-P7500 using XDA
Hey,
I'm sorry but i didn't solve the problem for me. With "shoot it up" I mean "i killed my phone". Sorry for that mistake!
I followed the guide too but at first step I flashed with Re-Partition and PIT file. Odin stucked at "Partitioning" so after 10min I closed Odin and restart S2...after that my device was completly dead. Screen stays black. Sorry don't know how to fix it. My S2 is on the way to rapaircenter now.
Aur0r4 said:
Hey,
I'm sorry but i didn't solve the problem for me. With "shoot it up" I mean "i killed my phone". Sorry for that mistake!
I followed the guide too but at first step I flashed with Re-Partition and PIT file. Odin stucked at "Partitioning" so after 10min I closed Odin and restart S2...after that my device was completly dead. Screen stays black. Sorry don't know how to fix it. My S2 is on the way to rapaircenter now.
Click to expand...
Click to collapse
I can access to the download mode but I can't flash anything through my beloved s2.
I am going to send it to the repair centre, u suggest me to send them to Samsung's or others??
Go into recoverymode and install a rom in ur memory internal or extaernal
Just do that turn off phone...and them volume up+power+home button u will enter in recovery mode not in download mode...now just search the rom ...notice u do this if its rooted... Look if u just put insecure kernel by odin i sugere u take sd card out download a rom by computer to sd card. input again in phone and turn on in recovery mode... i think will works im not responsabile for nothing can happened but im pass the same like i write...tell something
Sent from my GT-I9100 using XDA
Look the guy up say to you a dificult way to do and also u may brick ur phone...u do somethings in odin i just never do...i just saw now otherwise u already fix it if i put this earlier
Sent from my GT-I9100 using XDA
After try to recover my S3 ('cause i get a brick the typical problem that Samsung screen and then nothing happend, i put my cell into download mode and then try to flash only with PDA file i got the next error "There is no pit partition" ), following this steps from another post
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
i take the
4.1.2
I9300XXELLA_KOR_MULTI_FACTORY
i got a new message from Odin
see image1 in attachements
Now i don't know what to do... just i know is a little hope 'cause it can start a downloading mode...
So Please HELP!
there is the problem
<ID:0/005> Added!!
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Same problem
GaboBigale said:
there is the problem
<ID:0/005> Added!!
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What i need to do...!!! PLEASE HELP
Click to expand...
Click to collapse
Got the same problem man, if you resolve it first, let me know.:good:
Same problem
lumogox said:
Got the same problem man, if you resolve it first, let me know.:good:
Click to expand...
Click to collapse
got this same problem also, please, anyone? any help?
pit file missing
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
re-partition fails
panais86 said:
you have to download pit file so it can create a partition. download it and flash it together with the tar file of your desired firmware. i had the same problem but it couldn't create a partition as it is full bricked and i sent it for a warranty
Click to expand...
Click to collapse
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try to flash only the .PIT file.
you have nothing to loose
nand problem
echoen99 said:
thanks for the replay, unfortunately i have already tried that, it fails every time i am trying to re-partition.
Click to expand...
Click to collapse
try this link
http://www.droidevelopers.com/f363/...-files.html?11722-Download-OPS-amp-PIT-files=
if you have a problem as well then probably you have a problem with nand so you have to send it for warranty as well
Thanks for all the replys, i will check and update
Thanks
Sent from my GT-I9300 using Tapatalk 2
stuck same problem
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
mlijfu said:
hi
i have a smasung galaxy s3 international I9300
i think i soft bricked it cause i can go into download mode but when i swithch on the phone it gives me a screen
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
how i reached here was i flashed my phone with 3-4 roms got bit stuck and then removed my battery in the middle of a reboot there here i was
so i used ur RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
pls help
Click to expand...
Click to collapse
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Scarface1991 said:
What ROM and what Kernel did you use before it happened (Kernel version is also important)? And what did you mean with you got stuck? Details are important when you are dealing with cases like this.
I saw this kind of screen before, some guy had the same problem. However he couldn`t fix himself. Ever heard of Sudden Death?
Click to expand...
Click to collapse
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
mlijfu said:
thanks for the reply
CyanogenMod 9 stable version with its own kernel
i installed it and the gapps with it then when the phone rebooted it got stuck at lock screen then i reebooted it again but it was taking a bit long time at samsung logo so i took off the battery and there the phone became like this
//i276.photobucket.com/albums/kk29/mlijfu/photo.jpg
i can go into download mode
ODIN MODE
Product name:
custom binary download:no
currant binary: samsung official
system status : custom
as u can see product name is blank
with odin i tried ti flash stock Samsung firmware - it wanted some pit
so i used RESCUE FIRMWARE SGSIII I9300 - I9300XXEMC2_KOR_MULTI_FACTORY
same used in the first thread
but did not help
i got this
//i276.photobucket.com/albums/kk29/mlijfu/Untitled1.png
//i276.photobucket.com/albums/kk29/mlijfu/Untitled.png
Click to expand...
Click to collapse
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
This is half sds. Needs to go to a service centre and have the motherboard swapped probably
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will a Samsung Galaxy S III JTAG Brick Repair help me ?
mlijfu said:
will a Samsung Galaxy S III JTAG Brick Repair help me ?
Click to expand...
Click to collapse
No one has been successful with that method yet. The issue will be that the wear levelling bug has wiped out your eMMC and it needs replacing.
Have a read in the general forum of the "ultimate SDS thread" or whatever its called. There is also my "important - are you covered" thread stuck at the top of general.
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
KayKrate said:
So thats the sudden death ? Were you on 4.1.2 before you bricked?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
before rooting was on what ever the latest firmware was
i did not use triangle away
i was using paranoid android 4.2.2
then went to cmod9
so i think i am screwed
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
People gotta take care what firmware to flash :/ Stock 4.1.2 is safe , I used DFG and didnt get any freeze for like a week so my phone's stable now ... maybe samsung come up with a new firmware which makes your phone explode or ruin our devices ... Who knows >.< ?
rootSU said:
CM9 has no SDS fix.
All you can do is try and get warranty repair if you're still in warranty. Otherwise pay for a Mobo repair / replacement.
Someone posted a how to to fit a new eMMC and the cost of the eMMC was cheap, but the effort was a lot.
Click to expand...
Click to collapse
will this help i know its not for s3 but still as am desperate
1. ://forum.xda-developers.com/showthread.php?t=1670651
2. ://forum.xda-developers.com/showthread.php?p=26428986
3. //forum.xda-developers.com/showpost.php?p=26285877&postcount=12
just wanted to know from an expert will one of then work for me?
Hi,
I've got this problem with a friends(girl) phone.
Her phone was stuck at the firmware upgrade screen(the one with firmware upgrade encountered an issue). So she searched the internet for a solution and did some things with kies and odin. But nothing worked so i offered to help her.
So i searched and found this article. i followed all the instructions and downloaded 3 different versions of odin V3.07, V1.3 and V1.85.
Specifications of the phone:
samsung Galaxy S II GT-I9100 16GB
what i've tried so far:
i followed the instructions from te link above and tried it with the following roms
-I9100GXXLB1_I9100GATOKL1_ATO
-I9100XWLP9_I9100KPNLP1_KPN
-I9100XXLSJ_I9100OXXLS1_OXX
i also tried the gingerbread and the ICS version
i also tried the pit file. but nothing works, the progress get stuck like in this example
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help me with this problem? I also have a JTAG programmer but don't know how or what to do with it.
Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Look for hopper8's thread.
And stop flashing pit files.
Sent from the little guy
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Basseytje said:
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Click to expand...
Click to collapse
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
when u go to download mode, does it show your model number??
Hopper8 said:
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
Click to expand...
Click to collapse
I've already tried that one but odin is stuck at data.img.
tornado92 said:
when u go to download mode, does it show your model number??
Click to expand...
Click to collapse
Yes it shows the product name.
Basseytje said:
I've already tried that one but odin is stuck at data.img.
Yes it shows the product name.
Click to expand...
Click to collapse
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
tornado92 said:
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
Click to expand...
Click to collapse
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Basseytje said:
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Click to expand...
Click to collapse
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
tornado92 said:
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
Click to expand...
Click to collapse
kies won't recognize the phone. the only 3 screens i can access are showed in the pics below. i've got 2 stock roms which don't work. after i tried kies, i immediately uninstalled it and left the drivers on the pc.
i40.tinypic.com/29gkdi1.jpg
i40.tinypic.com/qsnluc.jpg
i41.tinypic.com/2aep3yx.jpg
can't post any files yet.
I hope there is still someone who can help me...
odin is still stuck on data.img
If you say you've 'tried everything' (which everyone always says), then it's a service centre job. What else do you want anyone here to say ? No miracle fixes. If it were me I'd keep trying, it's almost always something really simple/small/obvious that's causing the flash not to work, and as we're not there looking over your shoulder at what you're doing, it's going to be almost impossible for anyone to say what that is (you have 'tried everything' after all).
is there a way to fix this with jtag?
Basseytje said:
is there a way to fix this with jtag?
Click to expand...
Click to collapse
Maybe. No one can say for sure mate. If you motherboard is really borked, it would have to be replaced nevertheless.
Remember that Jtagging leaves marks on your device, so you can kiss goodbye any warranty u might have.
"To err is human, to forgive is divine."
Sent from my SGS II
hey.. i had this problem too.. the only solution that i had is to use the galaxy note pit file and a stock rom for i9100 ... then the phone went back to normal ..but the memory went from 16 tb to 11.5 gb .. it was the only thing that made my phone work again..
i installed pit from galaxy note ..with and original stock firmware 4.1,2 then after install I did a factory reset via stock cwm and a clear cache ..and it worked.. a few bootloops and it went on:|
alexandru.j91 said:
hey.. i had this problem too..
Click to expand...
Click to collapse
You got so ridiculously lucky that I can't comprehend that it worked. Please don't advise others to do the same, I'd say what you did is normally a recipe for a hard brick. Don't flash files for other phones, let alone a pit file for another phone. Yes I know the note has the same hardware as i9100 but you know what? It's not an i9100.
Edit: Look at what you posted in your other thread:
alexandru.j91 said:
I hardbricked my phone about 3 months ago with the original firmware from orange 4.0.4 and I resolved the problem by putting samsung note PIT file ..but I don't have acces to all the memory on my phone ..I have almosst 12 gb from 16.. and my phone is getting wired ..and it is shutting off randomly since then .and to get it on again i have to remove the battery ..
Does anybody know how to get all my memory back for my phone? tx
Click to expand...
Click to collapse
I'd say that's a reason not to flash files from another phone.
i was just telling him that i had the same problem..not to do the same thing..because of the problem that I have got! i have told in my other post whathappened to my phone! and i know that my problem can be solved by rewriting the memorybut i don't know how!..
---------- Post added at 06:04 AM ---------- Previous post was at 05:05 AM ----------
what I did.. i did because of some threads on xda ..so I am not crazy ..I just told him what I have did.. I haven't advised him to do that ..because of the problem that i had .. and when I wrote what I have did to make my phone worked .. i hace told the fact that it shrinked my memory from my phone..
maybe i'm getting a little progress. when i try to flash a new bootloader. i see a progress bar on the phone. but odin is halfway stuck at sbl.bin
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Sbl.bin
everywhere i read, people are saying use different cables. i already tried the samsung s2 cable, a htc desire cable, 3 deal extreme cables and an other htc(dont remember the model) cable. but i'm getting the same problems. stuck at zimage or something else...
anyone?
Hi Guys,
When i switch on my S3 Device it's completely white screen, No sound or any other thing.
Also cannot access recovery, I can go to download mode.
I tried to flash stock rom of Sammy via odin, but get this error..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Appreciate if you anyone could advise how i can flash.
Thanks in advance
Sounds like your partition structure is damaged or destroyed.
If you have warranty then don't do anything apart from return for repair.
If you don't then your only hope is a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=9133315996732562
Follow the instructions exactly, but you're probably going to need a new motherboard anyway.
it seems that u need to take it to the services centre.. i've tried fixing several s3 via software method thats similiar to "theres no pit partition" thing but alls are fail.. replacing motherboard or emmc chip are the only solution.
boomboomer said:
Sounds like your partition structure is damaged or destroyed.
If you have warranty then don't do anything apart from return for repair.
If you don't then your only hope is a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=9133315996732562
Follow the instructions exactly, but you're probably going to need a new motherboard anyway.
Click to expand...
Click to collapse
Thanks mate, I will download and see whether this can be fixed since i do not have warranty
lawong said:
it seems that u need to take it to the services centre.. i've tried fixing several s3 via software method thats similiar to "theres no pit partition" thing but alls are fail.. replacing motherboard or emmc chip are the only solution.
Click to expand...
Click to collapse
Thanks for the advise mate. Is there anyway to flash PIT file and re-partition
That rescue firmware includes a pit file, hence why so important to follow the instructions.
Usually ticking the pit file in odin means an instant hard brick, so use with extreme caution.
Hello all,
I want to preface everything that while I know a bit about rooting and messing with the stock status of android phones, I'm still generally a newbie at this.
Last night I started experiencing problems with my phone. I was using it normally until it ran out of battery while in a call, but I figured this happened in the past so it shouldn't be a problem. I plugged it in, however it wouldn't boot up. The CM11.2 loading screen just wouldn't stop spinning. Booting into recovery and download mode was working fine, but I couldn't get into the OS. Since I wanted for a long time to upgrade my Jellybean to Lollipop (and found this thread http://forum.xda-developers.com/gal.../rom-cyanogenmod-12-1-nightly-builds-t3147661 just last night), I decided it's time.
I boot into recovery and try and backup my data, but as soon as I click, the device freezes. Fast forward 5 attempts later with 3 different SD cards, it would still do the same thing. Already annoyed, I decide just to factory reset/wipe data, in order to flash the new Nightly and Gapps. As soon as I click, same thing happens, the CWM freezes and I have to manually reboot.
I figured the CWM is corrupt and I started searching on forums what to do. Tried flashing a new CWM with Odin (specifically this) but now I can't boot into recovery anymore, only download mode. I'm scared of doing more on my own. The current state of the phone is that it stays frozen at the "Samsung Galaxy S2" screen, the one with the yellow triangle w/ "!". Could you please help?
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
noppy22 said:
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
Click to expand...
Click to collapse
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
I tried getting a stock firmware from Sammobile, specifically firmwares/confirm/14909/I9100XWLSU_I9100OROLS5_ORO/. I tried flashing it, and this happened:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWMS2_I9100BULS3_I9100VDFLSF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ricksis said:
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
Click to expand...
Click to collapse
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Anyway get a stock rom for your region from
sammobile.com
or http://androidfirmwares.net/Home/sgs2
or http://www.tsar3000.com/Joomla/inde...alaxy-sii-firmware&catid=55:samsung&Itemid=82
noppy22 said:
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Click to expand...
Click to collapse
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Ricksis said:
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Click to expand...
Click to collapse
I'm not sure you can expect anything. It's just a common problem. See if you can get it fully charged and try the stock rom with odin again. Also check out this guide
As I said it seems like there is a hardware problem, the battery is just where I would start. Once you can rule that out you can look elsewhere
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
Click to expand...
Click to collapse
I tried with multiple stock roms, but they all fail in the same stage. I bought the phone carrier free, and its code is GT-I9100 (no extra letters afterwards like a lot of S2s have). I also found another solution, but it stopped after NAND WRITE start.
Hopper8 said:
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: or here. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Click to expand...
Click to collapse
I also found this http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
I've had a quick look at the thread you linked to, and from what I understand, the OP is providing a way to flash the firmware partition by partition......
In theory, this is a good solution, but unfortunately, I don't know enough about the firmware structure or about the odin flashing process to be able to meaningfully pass comment on that method.......My uninformed instinct tells me 'why not'......but my practical, logical side tells me 'caution'....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
Click to expand...
Click to collapse
In Odin 3.07, everything but PDA is greyed out for me. I donwloaded v1.85 and tried the 3 part thing: Odin freezes at NAND Write Start!!, and as for my phone, there is no blue progress bar appearing on the screen in the first place while i'm in download mode.
Just tried the pit file solution as well:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
Things to check for odin flashing.......
1) firewall disabled
2) antivirus disabled
2) all Kies processes killed (use task manager)
4) run Odin as administrator
5) only use main board USB sockets (pc/laptop side)
6) make sure Samsung drivers correctly installed.
7) windows 8 & 10 may not allow odin to operate correctly.
8) Use official Samsung usb lead.....no cheap s**te off eBay
9) try all usb ports on pc/laptop
10) try different cables
11) try different PC's/Laptops.......
12) do the whole procedure multiple times.....Odin flashing is a bit like playing the lottery......it may not work the first 9 or 19 times, but for some reason, on the 10 or 20th attempt, it does.......
The only thing that will 'win the day' is perseverance......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
There is (possibly) a plan B.......
Are you able to get into recovery?
If you are, you *could* try flashing PhilZ recovery which will root your phone.....then you can give flashing a custom rom a try.......
You possibly still could go that route even without recovery......by (maybe) Odin flashing a custom kernel .tar and then flashing a custom rom......
(I'm not talking about the latest CM12. ....but an older KK or JB based rom.....they're far more stable and complete than the LP based roms.....)
http://i.imgur.com/rVnFwJM.jpg
I had a busy week and only could try some solutions today. Unfortunately, I think they ended up with the hardbrick of my phone, as I am not able to turn it on anymore, not even in download mode.
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
Click to expand...
Click to collapse
I'm not sure, but I kinda fiddled enough with ODIN for just the battery to be the cause. Of course I am no expert, but I see no connection between the battery failing and all the other problems: cwm11.2 not wiping cache/dalvik or performing factory resets, the option to only boot in download mode later, etc. When I plug the phone to the USB port, nothing happens anymore.
Sooooo... RIP phone? ...
Ricksis said:
Sooooo... RIP phone? ...
Click to expand...
Click to collapse
If you are sure there's nothing else you can try........
But, even though it's an old device, it's still going to cost money to replace it....
You mentioned that odin failed to recognise it......
Another *possibly* would be the USB socket......
It would account for the lack of odin recognition *AND* a dead (uncharged) battery which could lead you to assume the whole phone is dead.
The port may have been ok at the start of your recovery attempts, but they do wear out (especially on older devices simply due to wear and tear) and by the last attempt it could have failed......
The part costs pocket change on ebay and is relatively easy to replace....I've done it myself......
Here's a guide I wrote on replacing the board......
http://forum.xda-developers.com/showthread.php?t=2335961
http://i.imgur.com/rVnFwJM.jpg