Related
i'm dumb as a brick cause that's what i have...a brick. honestly, i'm not sure how i managed this. it was late at night and i've done so many things trying to fix. here's my current situation:
i followed a guide somewhere on what to do if you think you've bricked your phone. it involves a pit file, a system.tar.md5, a kernel.tar.md5, and a recovery.tar.md5.
using odin, i can successfully flash the system.tar.md5 and the kernel.tar.md5.
...but the recovery.tar.md5 fails almost immediately. i have also tried using odin to flash clockworkrecovery. it too fails almost immediately.
my phone will not power on. however, if i plug the usb cable to my computer and the phone, i get the big battery picture (like it's recharging) but the little flower-like 'busy' indicator in the middle is not moving.
Remove the battery. Hold volume down and plug the phone into your computer. It should enter download mode, enabling you to Odin back to stock.
i've already tried that. it fails at the end of the flash when odin gets to 'recovery.bin'
have you restored back to stock before with those files?
you might have a bad download. Try re-downloading your files and try with the new files.
yes, all the roms? i have on hand i have previously used before and they worked. now everything i throw at it fails when it gets to recovery.bin and the phone won't power on. when i press the power button, nothing happens. however, if i plug into my computer, i get the previously mentioned battery screen.
My suggestion is that if you're able to get into Odin, don't lose hope you should be able to get back to stock.
Also, i'm not sure what files and what thread you followed for returning to stock, but this is my GO TO thread for anytime i want a really fresh start from scratch.
http://forum.xda-developers.com/showthread.php?t=977493
use the downloads from that thread and follow the instructions. You will need to do some more work afterwards to get back to where you want, but it should get you up and running at least
P.S. - the recovery odin file in that thread is outdated i believe, so don't flash newer stuff from that recovery
for example, i have a DL09.tar.md5 file that i have used to successfully flash before. now, this is what i get in odin:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<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.rfs
<ID:0/007> dbdata.rfs
<ID:0/007> factoryfs.rfs
<ID:0/007> modem.bin
<ID:0/007> recovery.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i also have a EB01_DXC.tar.md5 file that i have successfully used before. now, i get:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<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.rfs
<ID:0/007> dbdata.rfs
<ID:0/007> zImage
<ID:0/007> recovery.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ok... i had weird things happen to me not too long ago and it turned out to be my USB cable.
It charges my phone but anything dealing with pc connection it bugged out
i bought a replacement online for about $3 on amazon from OEM store or something like that.
but first try to get your hands on another cable, or at the least try different USB ports on your PC, preferably the ones closest to the power supply and see if that makes a difference
djlim4 said:
My suggestion is that if you're able to get into Odin, don't lose hope you should be able to get back to stock.
Also, i'm not sure what files and what thread you followed for returning to stock, but this is my GO TO thread for anytime i want a really fresh start from scratch.
http://forum.xda-developers.com/showthread.php?t=977493
use the downloads from that thread and follow the instructions. You will need to do some more work afterwards to get back to where you want, but it should get you up and running at least
P.S. - the recovery odin file in that thread is outdated i believe, so don't flash newer stuff from that recovery
Click to expand...
Click to collapse
thanks. i already had the ci500_vzw_eb01_froyo_rel.tar.md5 file. it never worked for me. odin on win7 32-bit would stop working at the end. however, i never had that particular pit file. i'm redownloading the tar.md5 just to make sure. however, the link to the pit file in that article is no longer working. none of those 'dropbox' links have ever worked for me. i'm trying to google that specific atlas pit filename but i keep getting broken links. any pointers?
http://dl.dropbox.com/u/19519343/atlas_v2.2.pit
i just uploaded it to my db... hope it works for you
ok. i found that particular pit file somewhere else (atlas_v2.2.pit).
i'm a little confused about what you meant about the recovery files in the article you linked to. are you saying don't use the recovery files in that article?
yea, that's an old CWR
if you're just trying to get your phone up and running, that last step is not necessary... if your phone boots up initially after the first odin flash, you can proceed however you want from there
i'm going to try the first stuff first and see how that goes...but if i'm still in the same situation then, i'm tempted to go ahead and try that old odin recovery file since recovery seems to be where my issues are. doesn't seem like it could make it any worse. however, the link there doesn't work for that either. any chance you could spot me a link for that too?
p.s. really really thank you for the help!
yea no prob... i'll check back in later when i get home from work and see if you need anything else. Good luck.
http://forum.xda-developers.com/showthread.php?t=1046905
the CWR situation got kinda confusing at one point and i didnt keep up with all the little details until it sort of got ironed out... i know that the most current one is 3.x and that thread i believe has a few options to get that on. If not, look up GizmoDroid. He wrote up a very detailed post on Clockwork and the whole confusion behind it and cleared up some stuff, sorry gotta get back to work, dun have time to look for that thread.
http://dl.dropbox.com/u/19519343/cwm-recovery-ALL.tar
ok... that is the OLD CWR, but it worked for all the stuff pre-eb01 i think...
def not for comm rom or official froyo released stuff, but that's the recovery file that's in the link i first sent you.
if you want the updated clockwork, check post # 5 of this thread
http://forum.xda-developers.com/showthread.php?t=1082726
was kind of bored waiting for the ci500_eb01_froyo_rel.tar.md5 file to download. i plugged my data cable into the back of the computer and tried flashing this 'CWMRecovery_DJ05_DL09.tar.md5' file i had laying around. didn't work at first. then i tried doing it with the atlas pit file you so kindly provided. it worked! the very first time in 24hrs and 100s of tries that i've actually been able to flash anything having to do with recovery...
...but phone still wouldn't power on. i plugged it into my wall charger and tried to power on. no go. well, i left it there plugged in. about 5 minutes later, i turn around and the stock recovery screen is up! yay! even tho it was barking about being unable to mount /dev/block/st111 and /dev/block/mmcblk0p1 ...i'm still pretty excited...some kind of progress i guess
i'm beginning to think all my problems are coming from the mad-crazy flashing i was doing last night with a very low battery. intuition told me that was a bad thing but i was already having problems and my OCD wouldn't let me go to sleep without getting my phone back in working order. OCD bad. Sleep good. low battery bad. charged battery good.
hey that's good news, at least there's some progress.
Will be offline for a while, but i hope there are enough links there for you to tinker with and hopefully get everything fixed.
i'm just glad my "bricked" folder of my dropbox finally got some use
YES! using that atlas pit file, the froyo rom linked there, and somewhat charged battery i am up and running!!!!
thank you thank you thank you!
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Fuzz21 said:
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Click to expand...
Click to collapse
Yeah, I'm reading this now. I just did what it said, but still no dice.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
I had a problem with mine where Odin wasn't doing anything at all. It would start but never finished. I changed the USB port and was good after that. Weird because my sgs2 and sgs3 international were fine using the one USB port. Just a thought to try a different port if it stops or fails
Sent from my SGH-I747M using xda app-developers app
brfield said:
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
Click to expand...
Click to collapse
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Problem solved!
JibbsIsMe said:
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Click to expand...
Click to collapse
OK, I got it. First, I followed this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I stopped right after step 8. I then put my Ext SD into my old phone, formatted it, and put on this: http://forum.xda-developers.com/showthread.php?t=1732191
Then I went into recovery, and flashed that ROM. Then rebooted, and I'm fine now! YAY!
I almost wasted $730....
--Jeremy
Awesome stuff !!
Mine is still a 500$ paper weight, LOL hopefully I can fix it :S
Good luck, I would hate to lose my phone on it's first day...
JibbsIsMe said:
Good luck, I would hate to lose my phone on it's first day...
Click to expand...
Click to collapse
Thanks budd
I really hope I can resurrect it from the Dead.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
I hate to threadjack, but this is the only thread I can find mention of this error with the sgs3 with.
mine did the same thing last night, thought I bricked.. but it didnt brick, used the phone all day today with no problems, tried to root again today with at&t method with odin, and I keep getting the same error. Its a bell i747m using odin 3.0.7
Any ideas?
Edit: Also I have tried several usb ports and a couple different cables.
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
I found that sometimes its all in the technique of how you plug things in and the usb used. Try different usb cords. Try different usb ports. and then for some reason what worked for me is have odin open plug usb into computer, and then put the phone into download mode and finally connect the microUSB into the phone. Hope it works, hit back if it does or doesnt
[email protected] said:
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
Click to expand...
Click to collapse
How long did you let it go for on the factoryfs.img?
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
creepyncrawly said:
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
Click to expand...
Click to collapse
I have tried it on all usb ports that I have on my laptop.
OK here's exactly what I did to my phone:
I downloaded the ICS version for i777 from sammobile and flashed it using ODIN. Then, I installed Siyah kernel using mobile odin. I then installed triangle away to get rid of the flash counter. I used my phone like this for a couple of days. Then today, I installed the AOKP rom. To do this, I first back up using CWM, then i booted in CWM recovery mode, did a complete wipe, deteled cache and dalvik, and then I proceeded to install the rom. Installation worked fine and everything, however the data wasn't working on my phone. So I then tried to enter the T-Mobile APN settings (it's an unlocked phone), however I couldn't save the APN settings. Tried to enter them multiple times and selected save from the menu, but it just wouldn't show up on the APN list. So, I tried to restore to my back up in CWM restore, however that failed. Admittedly, I should have asked for help at this point. However I was frustrated, so I decided to just use Odin again to flash the ICS stock firmware that I got from sammobile. However, it failed and had some error along the lines of completed writing but operation failed? I tried switching to different USB ports and restarted Odin with run as administrator, but kept getting the same error. On one of these numerous tries, I also tried to check the re-partition option just to see if that would change anything (probably not a very smart idea). Anyways, at some point during these numerous attempts, it got to the point where the phone wouldn't boot up and asked me to connect to samsung kies to restore. I tried that but my phone won't connect with kies. I then found your one-click odin stock firmware thing on these boards and used that. Tried multiple times at different ports, but it keeps getting stuck at factoryfs.img. I have left it in there for a good 30 minutes in this current try (4th). Also, this may or may not be relevant, the flash counter keeps going up.
PS: This is my first android phone so I'm pretty new at this, but I did try to read up a lot before trying anything (well, except for when I randomly checked re-partition that one time).
Edit: Sorry I should have made this clear - even though the phone will not boot, I can still get into download mode.
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
creepyncrawly said:
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
Click to expand...
Click to collapse
'
Thank you for the swift response. No, I am unable to get into recovery mode. It goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
While I didnt have your issues. I also recently bought an i777, my install went very smooth, everything worked more or less on the first try tried diff cords, ports and then finally it was the plug sequence that did it for me. Upon flashing AOKP, I immediately unlocked the phone via that galaxy S unlocker, I followed the steps to the T and my IMEI is still the same. I am also on tmobile, with working edge. I still have the pesky triangle, but I havent read too many good things about the triangle remover.
Perhaps you have a bad rom download? It might sound silly but flashing AOKP for a friend when I redownloaded the rom, everything worked fine. What the guy above me said, try recovery mode instead and then go from there. Good news is that your phone doesnt sound borked
creepyncrawly said:
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
Click to expand...
Click to collapse
Ok I tried this, and it completed successfully in Odin, however, the phone now gets stuck on the "Samsung Galaxy SII GT-I9100" screen.
But will it boot into recovery now?
creepyncrawly said:
But will it boot into recovery now?
Click to expand...
Click to collapse
No, it still does not boot into recovery.
OT: How long will I have the 5 min restriction on posting?
Also, I don't know if this is relevant, but when I try to turn off the phone, it turns off but then it'll automatically start back up within a few seconds and then get stuck on the samsung galaxy sII screen
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
creepyncrawly said:
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
Click to expand...
Click to collapse
No, I didn't put a pith file. Also just to make sure I'm flashing the right file, is it the one called "I777 UCKH7 stock param.lfs"?
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
creepyncrawly said:
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
Click to expand...
Click to collapse
It was the UCLE5 file. I'll try this one.
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.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> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
[email protected] said:
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.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> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
Click to expand...
Click to collapse
OK I tried it on all the USB ports that I have on my laptop. No luck. Still getting stuck at Sbl.bin. Any more ideas?
Yes. If it were my phone, I would start by flashing the param.lfs by itself and see if that allows it to boot, or makes progress.
If not, then I would flash the sbl.bin by itself and see if that allows it to boot, or makes progress.
If still not, then I would try the full UCKH7 package with the PIT file, and repartition checked.
You can get all the files from the Download Repository. Please bear in mind that there is risk in everything you are doing, (and have been doing.)
Hello guys!
First of all, I'd like to say Hi to everyone here, because it's my first post, even if i was seeking and reading forum earlier.
Okay, so from the beginning.
I got that phone from a girl who tried to unroot it and change FW. Now, the phone just boots, and stucks on the bootscreen, or goes to Download Mode, and:
1. I don't know what firmware it really is.
2. IMEI is still unknown, until tomorrow, i hope so.
3. I tried to flash everything, just EVERYTHING and:
- I can flash all kind of PIT files, hadn't tried with custom PIT's
- Also, I'm able to flash all kinds of bootloaders, but without any visible changes in phone
- I made my own JIG USB PLUG, but no matter how hard i tried, it didn't work (i'll try tomorrow with 301k, instead of 300k, but i think it's too small difference to work different)(+++ it didn't work even with older bootloader, even with two types of turning off the phone)
- Phone is recognized by system as Samsung Device, but after bootscreen stucking, it changes to an unknown device.
- Flashing kernel ends up with boot.bin and stucks
- Flashing other stuff ends up with NAND Write Start!! or zImage etc.
- I tried all versions of Odin.
I'm getting tired after 4 days, and nights of trying to rivive that screwsung (sry, i'm really mad )
So, again: What am I supposed to do? Any ideas?
Thanks in advance,
CU tomorrow!
celu said:
Hello guys!
First of all, I'd like to say Hi to everyone here, because it's my first post, even if i was seeking and reading forum earlier.
Okay, so from the beginning.
I got that phone from a girl who tried to unroot it and change FW. Now, the phone just boots, and stucks on the bootscreen, or goes to Download Mode, and:
1. I don't know what firmware it really is.
2. IMEI is still unknown, until tomorrow, i hope so.
3. I tried to flash everything, just EVERYTHING and:
- I can flash all kind of PIT files, hadn't tried with custom PIT's
- Also, I'm able to flash all kinds of bootloaders, but without any visible changes in phone
- I made my own JIG USB PLUG, but no matter how hard i tried, it didn't work (i'll try tomorrow with 301k, instead of 300k, but i think it's too small difference to work different)(+++ it didn't work even with older bootloader, even with two types of turning off the phone)
- Phone is recognized by system as Samsung Device, but after bootscreen stucking, it changes to an unknown device.
- Flashing kernel ends up with boot.bin and stucks
- Flashing other stuff ends up with NAND Write Start!! or zImage etc.
- I tried all versions of Odin.
I'm getting tired after 4 days, and nights of trying to rivive that screwsung (sry, i'm really mad )
So, again: What am I supposed to do? Any ideas?
Thanks in advance,
CU tomorrow!
Click to expand...
Click to collapse
Let's start with a model number. It'll be on the label underneath the battery.
ctomgee said:
Let's start with a model number. It'll be on the label underneath the battery.
Click to expand...
Click to collapse
Model number? You mean GT-I9100 or what? I thought it's obvious, so i didn't mention that...
+ I got the IMEI (I feel like an idiot, forgot it is sticked under battery) - first two digits: 35 (someone in some thread found it useful, so maybe it will be useful again)
celu said:
Model number? You mean GT-I9100 or what? I thought it's obvious, so i didn't mention that...
+ I got the IMEI (I feel like an idiot, forgot it is sticked under battery) - first two digits: 35 (someone in some thread found it useful, so maybe it will be useful again)
Click to expand...
Click to collapse
Not so obvious, really. I've seen more people I can count who have different models of SII come to this forum and flash random I9100 stuff to their SGH-I777/SGH-I727/SGH-T989/SPH-D710/SCH-R760/whatever.
Anyways, if you can get to download mode, just try flashing an original Samsung stock firmware. I recommend 4.0.3 or earlier. You can download one from www.sammobile.com.
Also, you said you can flash all sorts of PIT files. What PIT files? If you happened to flash a PIT file NOT meant for an I9100, you may have screwed the pooch.
ctomgee said:
Not so obvious, really. I've seen more people I can count who have different models of SII come to this forum and flash random I9100 stuff to their SGH-I777/SGH-I727/SGH-T989/SPH-D710/SCH-R760/whatever.
Anyways, if you can get to download mode, just try flashing an original Samsung stock firmware. I recommend 4.0.3 or earlier. You can download one from (link).
Also, you said you can flash all sorts of PIT files. What PIT files? If you happened to flash a PIT file NOT meant for an I9100, you may have screwed the pooch.
Click to expand...
Click to collapse
I mean, PIT files of the same type, but from different sources (each one was meant for an I9100)
I tried that one, stucks at NAND Write Start!!... Maybe I'm doing something in wrong order?
I need to go to sleep, really, I don't want to screw something up because of my tiredness. I'll be back in a few hours, and for the moment, thanks for help
celu said:
I mean, PIT files of the same type, but from different sources (each one was meant for an I9100)
I tried that one, stucks at NAND Write Start!!... Maybe I'm doing something in wrong order?
I need to go to sleep, really, I don't want to screw something up because of my tiredness. I'll be back in a few hours, and for the moment, thanks for help
Click to expand...
Click to collapse
We have the same model of SGS2 and tried the same. It also stucks in the bootscren.
celu said:
I mean, PIT files of the same type, but from different sources (each one was meant for an I9100)
I tried that one, stucks at NAND Write Start!!... Maybe I'm doing something in wrong order?
I need to go to sleep, really, I don't want to screw something up because of my tiredness. I'll be back in a few hours, and for the moment, thanks for help
Click to expand...
Click to collapse
I'd also make sure your cable is good, and is connected directly to a port on the computer instead of through a USB hub, or a port on your keyboard, monitor, or other pass-through port.
Hello again.
I've just came home, and first of all, I've tried a few wires, all original, two from Nokia, one from HTC, two from Sony Ericsson, all with the same result.
One thing I want to ask you is that i don't really know which thing i need to flash first, kernel or firmware.
As far as i know flashing ICS Kernel with Gingerbread firmware may cause softbrick, or even hardbrick.
I've tried everything you said and I'm still stuck.
Thanks for your replies.
celu said:
Hello again.
I've just came home, and first of all, I've tried a few wires, all original, two from Nokia, one from HTC, two from Sony Ericsson, all with the same result.
One thing I want to ask you is that i don't really know which thing i need to flash first, kernel or firmware.
As far as i know flashing ICS Kernel with Gingerbread firmware may cause softbrick, or even hardbrick.
I've tried everything you said and I'm still stuck.
Thanks for your replies.
Click to expand...
Click to collapse
Firmwares will contain a kernel. Thus, if you want a custom kernel, you would have to flash a firmware first, then the custom kernel. Otherwise, if you do it in the reverse and flash a custom kernel first, then the kernel contained in the firmware would overwrite the custom kernel.
And you are correct that you cannot use ICS kernels with GB, or GB kernels with ICS.
Try following the instructions in this thread for the original I9100 model: http://forum.xda-developers.com/showthread.php?t=1457458. They are the first two sets of instructions labelled "GINGERBREAD VERSION" and "ICS VERSION". I would try the ICS version first.
ctomgee said:
Firmwares will contain a kernel. Thus, if you want a custom kernel, you would have to flash a firmware first, then the custom kernel. Otherwise, if you do it in the reverse and flash a custom kernel first, then the kernel contained in the firmware would overwrite the custom kernel.
And you are correct that you cannot use ICS kernels with GB, or GB kernels with ICS.
Try following the instructions in this thread for the original I9100 model: http://forum.xda-developers.com/showthread.php?t=1457458. They are the first two sets of instructions labelled "GINGERBREAD VERSION" and "ICS VERSION". I would try the ICS version first.
Click to expand...
Click to collapse
Just to be sure: with Odin v.1.85?
celu said:
Just to be sure: with Odin v.1.85?
Click to expand...
Click to collapse
Any version of Odin should work fine, including 1.85, but I currently use Odin 3.04.
Odin is not recognizing my phone, v 3.04.
I'll try with older version.
EDIT:
Something is wrong with drivers, i'm reinstalling them, just a sec.
EDIT2:
Drivers are ok now, but:
Odin log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
EDIT3:
I was thinking about using Heimdall to flash, but is there any difference?
Is there any possibility to force flash kernel? Or even whole firmware?
celu said:
Odin is not recognizing my phone, v 3.04.
I'll try with older version.
EDIT:
Something is wrong with drivers, i'm reinstalling them, just a sec.
EDIT2:
Drivers are ok now, but:
Odin log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
Click to expand...
Click to collapse
So you never answered about the USB port - are you plugged directly into the computer? Have you tried other direct ports on the computer yet?
Last resort is to try a different computer altogether.
ctomgee said:
So you never answered about the USB port - are you plugged directly into the computer? Have you tried other direct ports on the computer yet?
Last resort is to try a different computer altogether.
Click to expand...
Click to collapse
I've got 3 USB ports (I'm using a laptop, also Samsung, if it matters), and tried all of them. Maybe I could be able to use PC tomorrow. Or i'll reinstall windows, because i'm using 64-bit version atm.
EDIT:
My father told me, that it could be broken "board to board header connector".. But i'm still trying!
EDIT2:
I've just had a small talk with samsung service manager, he told me that they had one phone that started to work after 24hours spent without battery. Seems a little bit silly, but why wouldn't i try?
EDIT3:
And so.. I'm loosing hope. JIG doesn't work, don't even turns on the phone. Kernel, or firmware can't be loaded at all.. I'm completely out of ideas.
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?