Hello I've bricked my sgs2 it's not so hard bricked. It goes to download mode easily, but the problem is I can't find 3 file rom - probably 2.3.6 android, cause every link on the interer is down [2011, 2012]. I tried flashing it with 1 file rom through odin but it fail. I need to repartition it with full 3 file rom.
Please is there anybody who can help me? Simply provide 3 file rom for odin with pit file for Samsung Galaxy S3 i9100...
Thanks
I have an untested 3 part + pit gingerbread (multi csc) firmware.....
I also have a 3 part jellybean firmware.
I can provide links to either or both of them if needed.....that is assuming your device is the international variant.....
http://i.imgur.com/rVnFwJM.jpg
@remialfa you didn't reply yet, but I'm guessing you still need the firmware....
Here are the links.....
Gingerbread
https://www.androidfilehost.com/?fid=24269982086991760
Jellybean
https://www.androidfilehost.com/?fid=24052804347838984
The Gingerbread zip contains a pit file, but the Jellybean one doesn't. There are posts on XDA that contain pit files, you just need to search for them.
http://i.imgur.com/rVnFwJM.jpg
Thank you I hope I will unbrick my sgs 2
You have a better chance of that if you use a pit with either of those firmwares than with just the firmware on it's own......
BUT......
You are advised to use the pit as a strictly LAST OPTION.
If flashing a pit fails, you end up with a device that CAN NOT be revived/recovered......
So...bearing that in mind, try with just the firmwares first.....The theory behind them is that they will format the partitions and erase ALL traces of previous software without rebuilding the partition layout....that is what the pit is for.....
And as I said, if the pit flash goes wrong, you end up with a device that has corrupted partitions which is then impossible to flash further.....
http://i.imgur.com/rVnFwJM.jpg
@remialfa let us know how you get on.....
What files you flashed, what procedure you followed.....
That way, if other members face the same issue as you, they'll know what to or not to try.......
http://i.imgur.com/rVnFwJM.jpg
I tried to flash 3 files rom. Fail. I tried different computer, different cables nothing helps. Then I tried to flash kernel. Odin froze on nand writing I need to shutdown Odin after 30 minutes. I tried flashing bootloader and also Odin froze and I turned it of after 30 minutes.
I have no idea what to do....
I can turn on the phone to the download mode... Only that.
Is this possible to unbrick this phone?
Flashing with odin is a bit like the lottery....
It may not work the first 9 or 19 times, but the time after that, it does....
Perseverance is the name of the game.
Look at this thread.....
http://forum.xda-developers.com/showthread.php?t=2345831
It has been written for situations like yours.....
http://i.imgur.com/rVnFwJM.jpg
Related
Hey guys need some help. I've gone through as much of the forums as possible and still trying to resolve this without having to send it away.
My brother's SGS II has the following symptoms:
-turns on and stays at the SGS II GT-i9100 screen (will not change)
-phone can enter download and recovery modes
-when phone is plugged in to charge the battery symbol will not show that it's charging then continue to the SGS II GT-i9100 screen...then back to the battery icon (and loop)
-attempts to reflash anything will either be successful or fail in ODIN but still results in the 1st issue above.
What should I try next?
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Are you using pit file when you flash with odin ? could be partition problem so using pit would fix that
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Thanks for the sarcasm my friend but when I say i've gone through most of the forum as possible I meant I've tried both those fixes to no avail...thanks anyway though :good:
leechseed said:
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Click to expand...
Click to collapse
yeah right now I haven't gone any pit routes yet. I've gone through both boot/bricked guides and right now it's a wash...hell i'm getting a loop between the battery screen and GT-i9100 screen now.
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
MistahBungle said:
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
Click to expand...
Click to collapse
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Doing the .pit and re-partition as we speak and hangs up on the exact spot...DATAFS (data.img). *sigh*
I'm going to try the bootloader option next. I know my bro says he's done it already but I want to be sure. Thanks for your help man.
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
here's another note...when flashing bootloader it comes up into the recovery screen and says "E: failed to mount /data (unknown error: 0)
trying a format data/system
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
yeah i'm comfortable with flashing pit files due to my weekly rom addiciton from my SGS/cappy hahaha
Anyway I may be experiencing that corrupt SD card issue i've been reading about...not sure.
sminky01 said:
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
Click to expand...
Click to collapse
Why dont you just try to flash a Stock Rom??
I would try that first - wipe - flash Stock (via CWM)
I always used the ONE file package of Roms and never had any probs..
Why on earth are you re partitioning with Odin? You know Odin isn't build for the S II, and the re-partitioning it does is for the Nexus or something. IE using Odin to re partition an S II royally ****s it. Flashing a PIT might work but why don't you just start at a logical place, before going out and doing a full manual JTAG on your phone with a pair of pliers, some masking tape and a bunsen burner, why don't you do the obvious. Which is update your Odin, uninstall Kies and reinstall it for the Samsung drivers, check the USB etc. something is clearly going wrong during the flash process despite it being "successful". Failing that, take it back to the shop, if your phone isn't a £500 paper weight by the time you read this, just apply for a new one. Make sure you erase any evidence of you messing around with it and return it.
sirknattar said:
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
Click to expand...
Click to collapse
The problem might be the Omega rom ??? is it compatible with I9100M series or just the I9100 the M could be the clue to the flash failing same as when Samsung released the I9100G and people who flashed that got screwed up with the incorrect bootloaders since the hardware is different in the I9100 and I9100G same problem might exist with I9100M
Thanks for everyone's help and suggestions. I've got a vague idea of the problem now and it's being sent back to Samsung for warranty (after I clear it with the JIG).
try to do the following.
1-flash any gingerbread CF kernel via odin
2-boot into recovery mode
3- wipe everything under mounts and storage including system partition
4-reboot into download mode
5-try to flash the CM9 Resurrection Edition
hope this helps mate. mine just emmc bricked on me, with the crappy LQ5 samsung firmware and had to RMA the bastard.
check ur pm mate
I would be very thankful to anybody who can help me recover my phone.
I have an S2.
I wanted to customize it so I embarked on my documentation on this forum.
I built quite an understanding about what the steps are.
For a lack of a centralized guide I resorted to using
http://forum.xda-developers.com/showthread.php?t=1311081
wary of the flash counter issue.
I was well aware that this thread is for the AT&T version.
I managed to root succesfully (ZergRush).
Unfortunately I had to take a long break in the process (2-3 months). When I came back I only selectively remembered all the caveats.
So the fact that the guide is not for the i9100 version escaped me.
Focused too much on the details of getting the process right that the big picture went past me - I was on the wrong forum!! (((
I installed MobileOdin, and obliviously got the latest Entropy kernel.
It installed OK.
However my home and back buttons stopped working.
Upon realization of my mistake (i777 kernel over i9100 hardware) I tried to recover by installing a CF-Root version (Unfortunately my original kernel version was lost, so I had to guess the version by reading posts with similar situations - Orange UK i9100)
I found a post suggesting to install
CF-Root-SGS2_XX_OXA_KG3-v4.1-CWM4.zip
Again I used MobileOdin but this time at reboot the phone hangs on the welcome logo screen.
If I boot into recovery I get the CWM menu alright.
However I get a list of errors at mounting recovery - see attached photo.
If I select anything from sdcard I just get the fedora hat logo and nothing shows up - have to go back by pushing power.
Any help is very apprecitated - how can I get a proper kernel in?
SDCards do not seem to be read either, just the hat logo and nothing happens.
How can I get a zip with the kernel onto the phone storage so to pick it up in CWM recovery and install it?
Thanks a lot for any input.
Can't you just flash a kernel (Siyah for example) through Odin (not Mobile Odin), or even flash a custom rom through it which replaces your kernel?
Sent from the Matrix
Donnie Sins said:
Can't you just flash a kernel (Siyah for example) through Odin (not Mobile Odin), or even flash a custom rom through it which replaces your kernel?
Sent from the Matrix
Click to expand...
Click to collapse
Thanks for the quick reply.
If I use Odin won't that increase the pesky flash counter?
I would much rather flash a stock kernel, would that keep the counter the way it is?
If so, could you please link me to a stock gingerbread stock kernel?
Many thanks
DorinAlex said:
Thanks for the quick reply.
If I use Odin won't that increase the pesky flash counter?
I would much rather flash a stock kernel, would that keep the counter the way it is?
If so, could you please link me to a stock gingerbread stock kernel?
Many thanks
Click to expand...
Click to collapse
That's true, but why is that a problem for you? However, there are ways to 'reset' this counter (search for it here on xda if you really want this). If you have Siyah working, you can enter Recovery Mode again and you can start flashing.
Sent from the Matrix
DorinAlex said:
Thanks for the quick reply.
If I use Odin won't that increase the pesky flash counter?
I would much rather flash a stock kernel, would that keep the counter the way it is?
If so, could you please link me to a stock gingerbread stock kernel?
Many thanks
Click to expand...
Click to collapse
I think you should focus on your kernal problem first once you get the phone squared away then get the triangle away app to reset your counter
GT-I9100 powered by
NeatRom Lite 4.0
Philz kernal 3.81
Many40's battery tweaks
Flash a custom ROM via Odin, I suggest LiteingRom... Then go from there...
Sent from Valhalla :mwhahaha:
Can anybody confirm that if I flash a stock, non-custom, kernel :
1. The flash counter doesn't increase
2. The CWM recovery console doesn't get replaced
Thanks so much
1) Yes.
2) If you flash a stock kernel (or any kernel for that matter) you will have the recovery that comes with that kernel I.E standard Android recovery in the case of non-rooted stock (if you flash a CFRoot kernel, which is essentially a stock kernel with root, then you'll have CWM recovery). Recovery is baked into the kernel. You can flash temporary versions of CWM that will persist until the next reboot, but if you want CWM permanently, you need to run a kernel that has it.
MistahBungle said:
1) Yes.
2) If you flash a stock kernel (or any kernel for that matter) you will have the recovery that comes with that kernel I.E standard Android recovery in the case of non-rooted stock (if you flash a CFRoot kernel, which is essentially a stock kernel with root, then you'll have CWM recovery). Recovery is baked into the kernel. You can flash temporary versions of CWM that will persist until the next reboot, but if you want CWM permanently, you need to run a kernel that has it.
Click to expand...
Click to collapse
Thanks for the prompt authoritative answers.
Given the above, can I also please ask for your suggestion to solve my problem?
i.e.: phone kernel is messed up, cannot boot, recovery is unresponsive when accessing storage. would like to keep flash counter down.
hopefully download mode works to flash new kernels (haven't tried it yet have to decide on the kernel)
Should I go with:
a) flash stock kernel using PC Odin, re-root, apply proper CF-Root custom kernel (flash counter not increasing?)
or
b) flash proper CF-Root using PC Odin (hoping counter doesn't increase)
In any case, can you be so kind as to direct me to the proper version of stock and CF-Root? The one I guessed by myself got me in this mess in the first place
CF-Root-SGS2_XX_OXA_KG3-v4.1-CWM4.zip
Or is this one right, if I don't mess it up again with Entropy?
All the kernels should be Gingerbread - since I am OK with rooting it without making a mess of myself.
Ideally, on top of the kernel names, could you please give me a URL to the location of the kernel files as well, if there is a recommended one.
Cheers
Much appreciated
Scenario A.
Your phone isn't working (I presume it's still not ?), your first priority should be getting the phone working properly. Back to stock, then you can root/flash another rom/whatever.
P.S - Forget the flash counter. You seem obsessed with it. It's irrelevant unless you have to return the phone for a warranty claim. In that case, reset the counter with Triangle Away if you're running recent firmware or a jig if you're running GB (and 'old' bootloader) at the time. At the very least worry about getting the phone up and running normally before you start fretting about flash counters.
MistahBungle said:
Scenario A.
Your phone isn't working (I presume it's still not ?), your first priority should be getting the phone working properly. Back to stock, then you can root/flash another rom/whatever.
P.S - Forget the flash counter. You seem obsessed with it. It's irrelevant unless you have to return the phone for a warranty claim. In that case, reset the counter with Triangle Away if you're running recent firmware or a jig if you're running GB (and 'old' bootloader) at the time. At the very least worry about getting the phone up and running normally before you start fretting about flash counters.
Click to expand...
Click to collapse
You are right I should worry about the phone. Probably in denial about it being bricked :s
So yes, get stock back in.
Considering I still have some data to back up from the phone before upgrading from GB to latest (phone was on GB before the messiness), I suppose it is better to get a GB kernel in, am I correct?
In this case, can I please kindly ask for the location of a stock kernel to download? Is it safe to get any version of GB in?
Thanks for helping me with this
If you're currently running GB firmware, the phone won't boot without a GB kernel.
Try Samfirmware or AndroidFirmwares.net. If you can't find the kernel you're after, download the entire rom & extract the zImage from the rom package. You can flash this in the PDA section of Odin. If you don't know what firmware you're running, you're going to have to flash an entire rom. In that case, it probably doesn't make much difference which rom you flash. If you flash an entire rom, you can probably kiss any data stored on the internal SD card goodbye tho.
DorinAlex said:
You are right I should worry about the phone. Probably in denial about it being bricked :s
So yes, get stock back in.
Considering I still have some data to back up from the phone before upgrading from GB to latest (phone was on GB before the messiness), I suppose it is better to get a GB kernel in, am I correct?
In this case, can I please kindly ask for the location of a stock kernel to download? Is it safe to get any version of GB in?
Thanks for helping me with this
Click to expand...
Click to collapse
Thanks to the nice people at http://androidromupdate.com/category/orange/ I was able to locate the exact version I was having since they are storing official versions for each operator.
So I am going to go ahead and try to reflash the correct kernel for my rom using Odin.
My first hurdle is that in Odin 3.07 when I select PDA the file selection box doesn't alow zImage to be shown in the window. I am able to select it by typing zImage.
Is this Ok to start flashing just having selected zImage as PDA?
Seems kinda hacky, especially since here is where you put the whole rom tar.md5.
Should I go ahead? What is the proper why to flash just the kernel with Odin?
Many thanks
The 'proper' way to flash a kernel in Odin is (if you have a package containing just the kernel) is to put it in the PDA section & flash.
Obviously you don't have that; you have an entire rom package & extracted the zImage, correct ? So obviously you'll be flashing that.
Pro tip: Don't use Odin 3.07, use 1.85 (If I see a post from you asking 'But whyyyy ???' I won't be responding. Just trust me).
So as I believe I've already said in a post the other day, you can flash the kernel on its own or the entire rom (which will obviously flash the kernel as well given the kernel is in the rom package). If you'd simply gone back & re-read what was said then, your phone would be fixed already. The instructions were pretty simple/clear.
So it's up to you what you flash. However, you've already been given every single bit of info (and some) you need to fix your phone. More posts when you could be fixing your phone is just delaying same.
I was just about to sincerely thank you for your help, but then again your attitude has surpassed any such attempt.
As a note of courtesy: if it's an ordeal to answer specific questions to well defined problems, don't. Nobody is forcing you to answer - I suppose there are members around here who are more helpful and polite in relating to people's problems. You know, people asking questions here are trying to discover knowledge you possess and have been given by others on your turn. You shouldn't be so anal giving back to the community.
As I was pointing out in my last thread - if you had bothered to comprehend it - what you were suggesting to do was not reflected in practice.
1. Odin doesn't accept zImage files for PDA - you have to hackingly add it in the file selector box.
2. There is no sign in its GUI that Odin accepts zImage file for PDA, as mainly the PDA box is used for full roms (.tar, .tar.md5)
I simply asked for confirmation that your suggested instructions - unnatural as they have turned out to be - are the right ones.
Usually when somebody suggests some actions that are not straightforward they try their best to express themselves eloquently. This wasn't the case, so I only wanted a confirmation.
But you've made it clear this time, think twice before asking for more info around here - incomplete/inaccurate information is something to deal with on your own.
Here is an update with the status of my problem.
I was able to guess out the missing information/step from the previous posts:
The file that goes into the PDA box in Odin has to be a tar file containing the various image files one needs to flash into the phone and not directly the zImage file.
Quick recap: I had a rooted phone with an original branded rom that I had successfully rooted. I flashed a custom kernel (Entropy) that was for the AT&T version of SGS2 and some buttons were not working. I then tried CF-root for Gingerbread (guessed version). After this the phone does not go past the original logo screen when booting. I used MobileOdin both times. Recovery is CWM 4 but I get cache errors, and no access to sdcard works. Download mode seems to be OK.
I have created a tar file with just the zImage file from the full branded rom that was on my phone. (I9100BVKJ4_I9100ORAKJ4_I9100BVKJ4_HOME.tar.md5)
Using Odin 1.85 I have used the newly created tar file to flash.
Everything in the window looks like Odin snapshots on guides all around the web. After clicking start in the first big box KERNEL is shown.
I get:
<ID:0/034> Added!!
<ID:0/034> Odin v.3 engine (ID:34)..
<ID:0/034> File analysis..
<ID:0/034> SetupConnection..
<ID:0/034> Initialzation..
<ID:0/034> Get PIT for mapping..
<ID:0/034> Firmware update start..
<ID:0/034> zImage
And then nothing happens.
I have tried on two laptops, rebooted, installed kies fresh on one of them with the same result.
I wouldn't flash the whole rom just yet, since I still hope to recover some data.
What could be wrong?
I have searched quite extensively for Odin info online but people didn't seem to come across something like this.
Thanks for any help
DorinAlex said:
Here is an update with the status of my problem.
I was able to guess out the missing information/step from the previous posts:
The file that goes into the PDA box in Odin has to be a tar file containing the various image files one needs to flash into the phone and not directly the zImage file.
Quick recap: I had a rooted phone with an original branded rom that I had successfully rooted. I flashed a custom kernel (Entropy) that was for the AT&T version of SGS2 and some buttons were not working. I then tried CF-root for Gingerbread (guessed version). After this the phone does not go past the original logo screen when booting. I used MobileOdin both times. Recovery is CWM 4 but I get cache errors, and no access to sdcard works. Download mode seems to be OK.
I have created a tar file with just the zImage file from the full branded rom that was on my phone. (I9100BVKJ4_I9100ORAKJ4_I9100BVKJ4_HOME.tar.md5)
Using Odin 1.85 I have used the newly created tar file to flash.
Everything in the window looks like Odin snapshots on guides all around the web. After clicking start in the first big box KERNEL is shown.
I get:
<ID:0/034> Added!!
<ID:0/034> Odin v.3 engine (ID:34)..
<ID:0/034> File analysis..
<ID:0/034> SetupConnection..
<ID:0/034> Initialzation..
<ID:0/034> Get PIT for mapping..
<ID:0/034> Firmware update start..
<ID:0/034> zImage
And then nothing happens.
I have tried on two laptops, rebooted, installed kies fresh on one of them with the same result.
I wouldn't flash the whole rom just yet, since I still hope to recover some data.
What could be wrong?
I have searched quite extensively for Odin info online but people didn't seem to come across something like this.
Thanks for any help
Click to expand...
Click to collapse
Expect the SMS and call logs , all your data is safe IMHO. Contacts are backed up in your google account. and Internal SD is not formatted in a factory reset.
---------- Post added at 12:30 PM ---------- Previous post was at 12:18 PM ----------
also don't worry about yellow triangle and try a custom kernel. You will be able to remove it eithr by USB jig (on GB rom) or us triangle away http://forum.xda-developers.com/showthread.php?t=1494114
DorinAlex said:
I was just about to sincerely thank you for your help, but then again your attitude has surpassed any such attempt.
As a note of courtesy: if it's an ordeal to answer specific questions to well defined problems, don't. Nobody is forcing you to answer - I suppose there are members around here who are more helpful and polite in relating to people's problems. You know, people asking questions here are trying to discover knowledge you possess and have been given by others on your turn. You shouldn't be so anal giving back to the community.
Click to expand...
Click to collapse
Jesus, get over yourself. Just thank the person that he or she had taken the time to post a reply and at least try to help you because I personally wouldn't and won't give you the time of day.
If you are too bone idle to look up the solution to your problem and check out other users past experience and knowledge then why should anyone else waste their time helping.
Sent from my GT-I9100 using xda premium
The last post is a monument of self-sufficience and lack of helpfulness.
mckeowngoo said:
Jesus, get over yourself. Just thank the person that he or she had taken the time to post a reply and at least try to help you because I personally wouldn't and won't give you the time of day.
Click to expand...
Click to collapse
Guess what, you just did. Just in your manner, of conceited aggressivity
If you are too bone idle to look up the solution to your problem and check out other users past experience and knowledge then why should anyone else waste their time helping.
Click to expand...
Click to collapse
This last one is awash with fallacy and misconceptions, that I just have to keep the flame going.
It shows a complete lack of understangind of how a forum works. It's not that the question asker expects the replier to do the work of searching.
A forum relies on the presence of experienced users (i.e. people who have previously gone through the pains of learning how a thing works) who are checking up what issues less experienced people are encountering.
If they are not so high on themselves the latter more experienced users, who are also keen to return to the community what they may have on their turn been taught previously by peers, when they see a problem they quickly know the answer to, will quickly reply and save valuable effort to the question asker.
It's not that every problem has a solution posted and you just have to "look it up" and you're saved.
Half true answers may delay more. Case in point.
The solution to just put zImage in PDA in Odin DOES NOT WORK.
You have to properly package a tar file, by following guides available on the forum. The wrong assumption that you can just put the zImage in the box has delayed me a lot.
It was false also that flashing the full rom will make me lose my data. I flashed the same version of my original rom and I got everything back.
So thanks to all who offered goodwill help.
Solution was:
Flashing same version of rom (official branded, easily traceable by operator and some basic memoryon officila firmware sites), full rom, that is.
This is a special case that requires extensive help from you guys (hopefully).
Problem: According to the ATT Samsung specialist the Bootloader I am using is corrupted
Attempted Solution: I have attempted to flash the stock SBL onto my phone but after trying every version of Odin3 (1.83-3.09) it did not work.
**The bar was entirely GREEN but it never finished**
Suggested Solution: Flash the stock ROM back onto the phone using Odin3
Outcome: After trying three different ROMs, all downloaded from Sammobile, using every version of Odin3 (1.83-3.09) only seemed to reach the end then fail at Modem.bin
I was wondering if anyone has any idea how to fix my phone, the original issue was that it never made it past the Samsung logo (not the Galaxy S2 Logo but the actual Samsung logo) the new issue is that it has the Samsung Galaxy SII Logo with the wrong model name (international model) and the small yellow triangle.
If my phone is permanently broken that's fine because I have a temporary phone I just want to get my files off of the phone before using my new one
I have a Jig
I can get it into Odin mode
I cannot get it into Recovery mode
I can get it into Factory mode
Help me please, I have no idea what else to do
Use this version of Odin, or just do more Google fu and find another place to download it from. [ http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 it may be the version of Odin you're using that's messing you up.
The link Phalanx7621 posted was supposed to point to the Download Repository (link is in my signature.)
The preferred version of Odin is 1.85. If you need it, the download link for Odin3 v1.85 at the top of the Download Repository is a working link.
If the boot loader was corrupt, the phone would be a true brick (no sign of life.) If the secondary boot loader was corrupt, the phone would not boot as far as the Samsung logo. It sounds to me like the AT&T Samsung specialist you received that information from was not fully informed.
The I9100 splash screen with the yellow warning triangle is due to flashing a custom kernel, so nothing to worry about. It can be cleared by flashing a stock kernel. Using the following procedure would have put that on your phone anyway by flashing the Siyah kernel, and then will removed it when stock Gingerbread is flashed.
Please note: The link in the Download Repository for the stock Gingerbread that you need to flash is not working, and I have yet to re-upload all these items to a new host. You will have to download this from the sammobile firmware page. It is the I777UCKH7 / I777ATTKH7 dated 2011 August. You'll need to sign in to download it. The registration is free. Edit: sammobile has not uploaded this file to a new host yet either. I will have to upload it and the sbl for you, but since today is Christmas, you may have to wait a day or two. At least you know that there will eventually be something to try.
Edit: The required files are now available with Dev-Host links in the Download Repository.
I think you will probably recover the phone by assuming it has nand read/write corruption and following this sequence:
Instructions to clear nand read/write corruption.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Attempt #1
When attempting to flash the Kernel in Odin3 v1.85 the bar was fully green but the program never said complete (I left it going for a few hours to no avail)
I tried flashing the SBL and the same issue happened, the bar was fully green but it never said complete (I had previously downloaded the SBL)
When attempting to flash the Gingerbread stock it does not even go past the SBL1 part, the bar does not have any green within it and the program still says NAND Write Start.
I'm not the best with this sort of thing but from observation it seems that my NAND is corrupt and isn't allowing anything to be properly flashed.
By the way: the Custom Binary Download now says: Yes (5 counts) which tells me that the phone recognizes that something is being flashed but it's not working properly
I'm back to being stuck and I think this phone may be truly broken :/
I don't think ur phone is broken.
Try a different usb/micro usb cable. Try a different usb port on ur pc (don't use a usb hub). Make sure the phone's micro usb port is clear of dirt/debris, etc.
Usually when i've had problems with Odin flashes it is something as simple as doing these things that results in a successful flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Same Issue
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
androidrequest said:
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
Click to expand...
Click to collapse
Did you follow exactly the sequence in post #3? If not, please try that.
creepyncrawly said:
Did you follow exactly the sequence in post #3? If not, please try that.
Click to expand...
Click to collapse
Yes, I tried that sequence exactly. It actually won't advance past #1. The green bar loads in Odin under kernel, but stops working at NAND Write Start. And trying the sbl ends with the same result (I believe it's the first download in the Download Repository). All of the flash attempts have failed or frozen, but the Custom Binary Download count is at 3.
I bought this phone off a guy on ebay who had accidentally flashed a stock N7100 rom on to this i605 phone. The phone still booted and everything worked but the cell radios because, you know, wrong bootloader and modem firmware.
For the life of me I can't get the modem or bootloader to flash with odin or heimdall, as they'll reliably fail at the same point every time (modem.bin or tz.img is what they fail at, whichever comes first. I've never gotten farther). So I figure partitioning must be slightly wrong then, but odin hangs on "get pit for mapping" when trying to flash the pit file.
Now with multiple firmware and stock firmware flash failures, you'd think it won't boot, right? As the act of wiping or over writing and failing would mess up anything on it, right? Well here's what I don't get: I can flash TWRP from heimdall, and then a CM zip from there (only contains boot.img) and it boots like a champ!
Long story short: Odin mode says i605, can run i605 versions of android, but I believe something is still wrong with the radios/bootloader/partitions that won't allow me to flash the proper firmware from N7100 to i605 to get the radios working. Help anyone?
Hi,
i try to repair the Galaxy S 2 (GT-I9100) from my cousin.
I don't know the internal size nor the original android version... (he can't remember)
I can boot into download Mode but not into recovery.
I tried to flash from linux and windoof using heimdall and Odin (differ versions).
Both programs don't show any error while flashing and the phone display the progress bar and reboots...
But no difference ... phone just display Samsung logo. And i can't start recovery mode.
Because i don't know the android-version or filesystem size i tried to flash different pits and bootloader but nothing is different to beginning...
With heimdall i get the current PIT flash an different pit-file and check md5sum - no differ ...
Has anyone a tip what i can try anymore? Or is it an nice paperweight ?
I tried this but it doesn't work for me...
http://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
Regards
erdo
There is a 'stickyed' guide in general by a member called hopper8. It's called 'Troubleshoot a failed odin flash'
Read the first post IN FULL and follow all the steps as many times as it takes to get your phone working....It sounds like there isn't any hardware issue with the phone, just that it's not accepting the flash.....sometimes it can be like that, and only perseverance will 'win the day'.....
If your device is the i9100 international variant, that guide has a link to a 3 part test/leak firmware which will have a slightly better chance of sorting the device than a normal firmware.....
It completely erases the device before flashing, so it gets rid of any leftovers that might be causing issues during a regular FW flash.....
http://i.imgur.com/rVnFwJM.jpg