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
Related
Hello, sorry if this has already been answered but I did look around at similar scenarios and it seems to me that using odin to flash the stock kernel should fix it but on my device, however, it doesn't fix my problem. I beleive what I did was select update firmware from .zip in clockwork on accident. Idk if this is what you consider a "boot loop" because it doesnt restart it just sits there at the black galaxy s2 screen. Any insight would be great. I hate to have to buy a new one as it is quite alot of money. Like I said, sorry if this is already answered but after looking around for hours I still hve had no luck. Thanks in advance, Alex
Can you get into recovery (volume up+home+power) or download mode (volume down+home+power)?
I can get in to download and recovery mode both
The outlook is promising then. Without knowing what you've flashed, it's impossible to say what damage you've done, but if you don't mind losing your data, you can certainly get back to a working state by following [READ THIS] Got a Boot Loop? Don't post a New Thread!.
Before going down that route though, if you do want to keep your data, let us know what you flashed as it might be recoverable (maybe you just flashed the wrong kernel).
I can't say for sure what i flashed but I can say that i either flashed with an update or updated with a kernel??? sound right??? idk. the data isnt near as important to me as the 680 dollars my carrier will charge me for a new s2. Right now im using a junk alcatel tribe and im going through galaxy withdrawls.
Well before flashing anything else, make sure you definitely have an I9100, not some other variant (I notice you mentioned dollars). If you have a different model, you're in the wrong forums and might make things worse by following advice for the I9100.
I was pretty sure that it is the I9100 but i took the battery out and double checked. it IS the I9100
also for what it's worth when going into recovery(stock version) right after the text reading updating application it gives me an error in red. (E:install_application_for_customer:Can't unmount /preload copy application failed) and after the (Appling [yes it really spells it appling] Multi-CSC) it says Can't access to '/system/csc/TTT/system/'. However, the line after it says that it says Successfully applied multi-CSC
My first attempt to get back to a working phone without losing data would be to flash a stock kernel then, have you tried that?
Ok.. done.. but it still sits at the galaxy screen except now it has the triange due to the custom firmware
If that hasn't got you up and running then it's probably time to bite the bullet and follow the instructions from the boot loop thread linked above (which will also remove the triangle).
Maybe you can answer another question for me. When in recovery mode it says apply update from sdcard... why does it say that when it doesnt actually read from the sdcard? i have checked with the sdcard both in and out and the file directory in the recovery mode doesnt change. is it calling the usb storage an sd card?
ok when flashing a stock rom do i use the phone option in odin or the pda still
If you're flashing a stock rom from [ROM+Guide]Official i9100 Firmwares KG, KH1/2/3/4, KI1/2/3/4/8, KJ1/2 Download, then just follow the instructions from there (but usually PDA).
:'( Still wont boot.
What does happen, did any steps fail, any error messages?
Everything went smooth with no errors. No steps failed. Sitting at the boot screen is all it does though
Did you definitely wipe user data? (step 3). The final step of that thread is to try flashing a ROM which wipes, such as (non-stock) VillainROM 1.1.
well... yes i definitely wiped the user data and it was successfull when doing so. I didnt try the villian rom just because I thought that it was an optional thing but i will def. try it now that you bring it up. and hey, i really appreciate the help no matter what the outcome
(VillainROM 1.1 - XWKE7 base) I'm a UHKG7..... is this going to be a problem? just something i noticed and thought I would ask before going ahead
Hello,
I have Galaxy S2 Canadian Rogers version SGH- I727R with GB 2.3.5. I wanted to Install a custom Rom into my phone for that i followed below
steps :
1. Root with CWM recovery
2. Wipe data
3. Installed this "http://forum.xda-developers.com/showthread.php?t=1824586" rom through recovery.
I rooted and installed CWM recovery successfully. wiped data successfully phone was ok till then.
after that installed the rom. Rom installation was successful as well. after that i select reboot phone but my Phone never Reboot.
I removed the battery for few minutes then put that back in and tried to start the phone but my phone is dead now. When i Flashed my battery was fully charged. so this is not a low battery issue.
What went wrong Here. Please can anyone Help me. How can i Start my phone again...Please..need help urgently
Can u enter recovery or download mode ?
Thats an ICS rom and you where on GB, you should never flash ics roms on gb
No i cant enter in Download or Recovery mode. If i could then this should be solved.
My phone is total dead now. Please give me any solution or tell me a way to turn my Phone On..
killer_nave said:
No i cant enter in Download or Recovery mode. If i could then this should be solved.
My phone is total dead now. Please give me any solution or tell me a way to turn my Phone On..
Click to expand...
Click to collapse
Wave a magic wand maybe??
If your phone is totally dead as you say what do you expect us to say other then get it fixed? You will need to send it away for JTAG flash or mobo replacement. Only thing you could try really is a USB jig see if it forces it into download mode.
Also why on earth create this topic when we have plenty of this EXACT same subject? no need to create another when you can go read them or reply if needed.
i just want to know, what went wrong that my phone is not starting?? i just followed every steps i found in the forum
but after flashing the rom all went wrong..
WITHOUT JTAG flash is there any other way left with the help of software i can start the phone???
Nope. As my learned colleague has already intimated, in scientific terms, your phone is Donald. Service centre or possibly JTAG repair by 3rd party repairer; will be cheaper than having Samsung/authorised repairer fixing/replacing it if it can be repaired this way.
killer_nave said:
i just want to know, what went wrong that my phone is not starting?? i just followed every steps i found in the forum
but after flashing the rom all went wrong..
WITHOUT JTAG flash is there any other way left with the help of software i can start the phone???
Click to expand...
Click to collapse
Good Lord.
You apparently know what your phone model is, because it's in the title of your thread.
The ROM you said you tried to install is an i9100 ROM. NOT a ROM for the SGH-I727.
MAYBE you should have made sure the ROM you tried to install was for your model of phone before you did so?
Your model has a totally different SoC than the i9100. That is what happened.
killer_nave said:
Hello,
I have Galaxy S2 Canadian Rogers version SGH- I727R with GB 2.3.5. I wanted to Install a custom Rom into my phone for that i followed below
steps :
1. Root with CWM recovery
2. Wipe data
3. Installed this "http://forum.xda-developers.com/showthread.php?t=1824586" rom through recovery.
I rooted and installed CWM recovery successfully. wiped data successfully phone was ok till then.
after that installed the rom. Rom installation was successful as well. after that i select reboot phone but my Phone never Reboot.
I removed the battery for few minutes then put that back in and tried to start the phone but my phone is dead now. When i Flashed my battery was fully charged. so this is not a low battery issue.
What went wrong Here. Please can anyone Help me. How can i Start my phone again...Please..need help urgently
Click to expand...
Click to collapse
I hate to be the bearer of bad news but your issue is one of two things. Galaxy S2 phones have something called the emmc brick. It often occurs when flashing a new rom from recovery. Unfortunately it is a hard brick, and is unable to be recovered from. For more details on the emmc brick there is sticky in S2 forum.
The other likely but equally unfortunate scenario is you flashed an improper rom that contained a kernel that was not intended for your device.
The symptom for both of these issues are a phone that does not turn on, as if you were trying to turn it on without battery in. Your best option is to have rogers send it off for repair as long as you remain within warranty period and be hopeful they don't refuse repair or replacement due to voided warrenty.
Wish I could offer you a better solution, and I wish you the best of luck in your situation.
Side note: just a couple comments directed at those who replied with less than helpful responses. Let's try a little to have some empathy for people. Chewing the ops head off for not replying in a pre established thread and for making a mistake and flashing the wrong rom is not productive at all and paints a pretty nasty image on us as a community. Consider for a moment the circumstances surrounding this thread, the op is likely stressing out or even worse panicking because he fears he has ruined his device and all we can do is berate him for his mistakes. Put yourself in his or her shoes.
Thank you.
Sent from my SGH-I757M using Tapatalk 2
skodazek said:
I hate to be the bearer of bad news but your issue is one of two things. Galaxy S2 phones have something called the emmc brick. It often occurs when flashing a new rom from recovery. Unfortunately it is a hard brick, and is unable to be recovered from. For more details on the emmc brick there is sticky in S2 forum.
The other likely but equally unfortunate scenario is you flashed an improper rom that contained a kernel that was not intended for your device.
The symptom for both of these issues are a phone that does not turn on, as if you were trying to turn it on without battery in. Your best option is to have rogers send it off for repair as long as you remain within warranty period and be hopeful they don't refuse repair or replacement due to voided warrenty.
Wish I could offer you a better solution, and I wish you the best of luck in your situation.
Side note: just a couple comments directed at those who replied with less than helpful responses. Let's try a little to have some empathy for people. Chewing the ops head off for not replying in a pre established thread and for making a mistake and flashing the wrong rom is not productive at all and paints a pretty nasty image on us as a community. Consider for a moment the circumstances surrounding this thread, the op is likely stressing out or even worse panicking because he fears he has ruined his device and all we can do is berate him for his mistakes. Put yourself in his or her shoes.
Thank you.
Sent from my SGH-I757M using Tapatalk 2
Click to expand...
Click to collapse
He was running GB, does the emmc brickbug also affects GB ? I thought it only affected 4.0.4 running stock kernel
Poroto said:
He was running GB, does the emmc brickbug also affects GB ? I thought it only affected 4.0.4 running stock kernel
Click to expand...
Click to collapse
no it will affect only the stock ICS v4.0.4, that to with the stock kernel's of those firmwares ma8
the OP's issue is mainly because he flashed a rom meant for i9100 on his phone, since both the phones i1900 and I727R have diff hardware altogether
i9100 - 1.2ghz with Exynos chipset and mali 400 gpu.
I727R- 1.5ghz with Scorpion chipset and adreno 220 gpu.
Hey I recently rooted my Samsung Galaxy S II I9100, at first everything was fine, but i had some trouble installing apps so i used es file manager to install them, it began to work for some apps. anyway, this morning I woke and turned it on and it didn't get past the bootscreen(i left it for about 45 minutes on one occasion, and I tried rebooting many times.
The first thing i did after attempting to boot my device was to flash the kernel again via odin, this did not work(tried twice).
so i did a lot of research over the past 10 hours into my problem and have tried many different things; installing a stock rom, removing battery, pretty much anything on the forums that people said have worked. nothing.
I can get into recovery mode and download mode.
I don't care about my data on my phone, it has already been wiped.
It's still covered by warranty so i can wipe the flash count(?) and send it in for warranty IF I HAVE TO. preferably not however.
although i highly doubt it, I may have been using the wrong rom, and I may have forgotten to reset my phone before one of the re-flash's
So if you havn't figured out my question by now, how do i return my phone to working condition?
Don't get mad at me for making a thread that has probably been made a hundred times, none of the solutions in the other threads fixed my problems, and I was browsing not only xda but other forums for hours, I found that reason enough to post a new thread. Apologies if this is in the wrong section, I am new here, and never found it necessary to create an account until now, when I couldn't find a solution.
Help is appreciated, this problem is really rustling my Jimmies on Christmas day.
because this is such a problem, I will REWARD anyone who presents a working solution that does not involve sending it off for warranty or buying a jig. Sorry if i missed out some information, please request for missing info in a response.
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
.
theunderling said:
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
Click to expand...
Click to collapse
originally i was on ics 4.0.3, and i used this tutorial galaxys2root.com/galaxy-s2-root/how-to-root-galaxy-s2-i9100-icsandroid-4-0/ (can't post url link because im a new user) and this kernel by the file name "CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5.tar". I then searched for stock roms for it and got "CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5.tar" and "CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar"
If you want a stock rom go to Sammobile,join(so you can download).....then input smartphone>android>your phone model>your country/carrier.
Choose whatever 4.0.3 it recommends after you input the above and hit send.
Then flash that with Odin and see what happens.
Then report back here.
I am from Australia and when I searched for roms for the I9100, no Australian roms showed :s
would one from another country work, or would that be locked or...?
Theres 3 listed for starters for the plain gt-i9100.....is that your exact model....or is it p/g/m etc.
This is why I asked for your model.
gt-i9100 is my model that's all it said in my phone information in the settings (before it stuffed up), manual, on start up and in download mode.
sorry, I'm not excellent with my technical android terminology.
false alarm, it just didn't load properly before, I will start a the download (will take like 15 minutes) and report back when i flash it. gt-i9100 is definitely my model.
You just input which one of these 3 applies,hit send,then download.
Then flash it (the extracted file)in download mode with Odin.
so i put the extracted file in the 'PDA' field, put it into download mode, plug it in and start the process?
Yep.
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Good.Wait til boxing day til you flash siyah-s2.v.4.1.5 kernel for root.......lol.
hehe... yeah... I'm not going to try root again... lol
syntaxibles said:
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Click to expand...
Click to collapse
Going back to your first post,maybe you could make a donation to one of the developers on this site of your choosing.
sounds good, which developer in particular would be a good choice?
I quite like Doomlord,but its up to you
And just post back on this thread if you need help rooting etc.
Hi Guys,
I have been scouring the boards and the internet on a solution to this problem.
GF had the phone and put it to charge.
Picked it up sometime later and it was off.
Turned it back on and it was stuck in a bootloop.
Phone was using Stock Firmware and was unrooted. It was running Jelly Bean 4.1.2. The EXACT firmware eludes me.
Phone is able to go into Download mode and recovery mode.
I have included a picture of what recovery mode looks like. [pic]
I tried flashing via ODIN. I tried different firmwares. All of them stopped at Boot.bin
I tried Kernel flash via PDA and it stopped at "NAND Write Start!" and just stayed there.
I tried flashing a bootloader and the progress bar appeared (only time it ever appeared) but it stopped after a little budge and did not move again. Not even after 30 mins. [pic]
Is there anything else I can do? I followed all the tips from http://forum.xda-developers.com/showthread.php?t=1449771 and I'm still here. Any insight would be appreciated. Thank you.
Hopper8's "Odin troubleshooting' thread. Find it, try the stuff in it. All of it. Not just try a few things & then post here saying 'I tried everything' when you didn't. The only thing that will happen if you do that is you'll still have a busted phone. And you need to try the stuff in that thread repeatedly. Over and over. As many times as you need to.
That's the only way you're fixing it (the alternative involves paying a Samsung service centre a considerable amount of money to fix it). There are no easy/simple fixes in these situations.
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
theunderling said:
Im pretty sure I was in exactly the same situation a while back.Youll need to look back at my posts as Ive forgotten exactly how I fixed it.
It did involve GB and pit files via odin as nothing would flash by recovery.
Im on 2.3.5 as that was about the only thing that would flash properly and make the phone boot.I initially thought I had a bootloader problem as ICS/JB wouldnt load.
I spent 5 hours on that,and cant recall if it was the pit or the special 2.3.5 rom/or both that fixed it.
Click to expand...
Click to collapse
Thanks. I'll search your posts.
I think I posted a pic with similar errors to yours,so look and compare them.Theres not much info floating around about our/your problem.Pit files are only meant to be a last resort option,and I was in that category.
I also think that most/all things I flashed with odin passed,but phone would not boot,which led me to flash 2.3.5 combined with pit file.
I can't find your posts.....
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
theunderling said:
Im only commenting because Im pretty sure its nothing to do with odin,I feel my phone and maybe yours has a hardware problem.I done a search before and only saw 1 situation like mines on another website.
For me,there was something major wrong for my phone not to accept ics/jb stock firmwares.
I have posted a pic before with the errors,and commented what I done to get the phone working.
I also dont think anyone on here can help,as it was the worst thing to fix Ive ever came across,and its not been mentioned on here.
Its up to you what you want to flash,but my moneys on a frankenstein GB rom c/w pit.Only try it at your own risk,or wait until someone else has alternative advice.
Click to expand...
Click to collapse
So I flashed the pit file.... and nothing happened. It just stopped there at "DO NOT TURN OFF TARGET!!!" I eventually closed ODIN but the phone still behaves the same way. If the EPROM is damaged, it won't have a partition to partition right? Any other suggestions?
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
levi_jm said:
I tried to flash CF root. Just to try anything. If hung up after kernel flash. Not it says I have a custom binary. Count 1. I don't know if that is relevant but... it shows something.
Click to expand...
Click to collapse
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
theunderling said:
Youll need to ignore half of my previous advice(about odin),and follow Mistahbungles advice.......as my memory is playing tricks on me.Also,it was the other way around in my case.....ICS/JB flashed ok,it was GB that wouldnt(but doesnt matter here).
You have a damaged partition table,so that hopefully will be fixed by flashing .pit using Odin.If you cant get Odin to work,you could try a friends pc,or see if a local shop has Odin working.
Apologies to you both for my memory.........lol
Click to expand...
Click to collapse
I did try his advice and with 6 different versions of odins on two different laptops with 6 usb ports between them. I don't think ODIN is the problem. I think the problem is a corrupted NAND. It is so corrupt that it did not accept a .PIT flash. It didn't hard brick the phone. It did nothing to it. I am unsure what else to do.
Well maybe I was right all along about odin,but that doesnt help anything.
I cant remember if I could do anything via recovery,but I do remember that several things I tried just kept giving that page of errors.
Youll just need to google each error and see what it throws up.Stuff thats said ranges from removing sd card to replace recovery(but by odin which you cant do).
I'm in a bit of a tight situation over here. My mom's phone was having issues, so she wanted me to fix it before I left to visit my grandparents. I found a stock ROM for the phone (GT-i9100 International) and flashed it, but the phone always got stuck on the "Samsung Galaxy SII GT-I9100" boot screen (occasionally it would show the "O2" screen, as it was a ROM for Ireland). I tried a different ROM (can't remember what country it was), and I'm still stuck with the same problem. This time no O2 screen though. I've downloaded my ROMs through sammobile.com and I'm using ODIN v1.83.
The label under the battery reads:
Model: GT-I9100
SSN: -I9100GSMH
What ROM should I use and where can I get it? I found this thread with a link to the ROM for the international version, but Hotfile has been shut down, so I can't download it.
Sorry if I could've found the answer with a few more hours of searching, but I've got less than 24 hours to find a fix and I was hoping that someone else could help me. Thanks a lot!
EDIT: I'm in the U.S., if that matters.
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Any region?
MistahBungle said:
Try AndroidFirmwares.net or Samsung-Updates.com. If it were me in that situation (I.E not my phone), I'd be putting whatever the latest firmware is for the carrier/country.
Click to expand...
Click to collapse
Should any region work to get the phone up and running? I just need to get it back up so that I can root it and flash CM10. Thanks.
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
MistahBungle said:
Yep absolutely. If your end result is to root the phone & put a custom rom on, use any stock rom you can get your hands on. Though I'd be avoiding 4.0.4, anything other than that should be fine.
Click to expand...
Click to collapse
Is 4.1.2 OK, or should I go for 4.0.3 or below?
Doesn't matter, take your pick.
More info on problem
I tried installing two other ROMs (from androidfirmwares.net), one 4.1.2 and one 2.3.6. The 4.1.2 didn't get me anywhere, but after I flashed 2.3.6 the phone said the assert check failed. GT-i9100 is on the list of what it checked for. (I've never had any luck with the assert checks on any of my Samsung phones: GS Captivate, GSII Skyrocket, or AT&T GSIII. I've always had to remove the check in my update script.) I attached a picture.
EDIT: Since the attachment doesn't seem to be working, here's a Dropbox link.
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
MistahBungle said:
Pic won't load for me, but it mentions 'recovery error', what exactly are you doing/what's the problem ?
Click to expand...
Click to collapse
My process:
Open ODIN v3.09
Plug in the phone, already in download mode.
Click the AP button and load my .tar.md5.
Click Start.
Wait for it to finish, leaving the phone untouched on the table.
I just tried another USB cable, but to no avail. I've also tried unplugging the phone right after it reboots and ODIN says "PASS!", but no luck there either. I just tried another ROM that just finished downloading and it's giving me a similar getprop() error. At the bottom of the output in red it says:
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I don't think there's any way for me to edit the update script, as the tar contains a bunch of filesystem images. Even if it was easy to edit it would ruin the checksum verification.
Check out the picture on Dropbox here.
What are you trying to do in Android recovery ? Given what your stated aim is - get a stock rom on the phone, re-root it, put custom rom on, you shouldn't be using Android (I.E stock) recovery at any stage.
The process should be:-
*Flash stock rom with Odin in download mode (I.E phone off - home/vol down/power, not home/vol up/power)
*Root phone with whatever method
*Flash custom rom with CWRecovery, which you'll get once you root the phone
So....You need to go step by step. Start with flashing the stock rom with Odin, and try to boot the phone normally/make sure that was successful before doing the next two steps. Look for Hopper8's 'Odin troubleshooting' guide if you're having trouble getting a successful Odin flash.
Once you've done that, root the phone & make sure you have CWRecovery working, then flash the custom rom.
The phone boots to the recovery screen after it finishes flashing with ODIN. I put it into download mode, run ODIN, and then it that error screen comes up on the next reboot.
Try flashing the three part firmware linked to in Hopper's thread first (this will wipe the phone). I can't help but think we're missing some info re: what's been done to the phone previously here if the phone is booting into recovery mode after being Odin flashed. It shouldn't do that. After an Odin flash/pass the phone should boot normally, assuming it's not a case of the NAND being corrupted (it probably wouldn't boot into recovery if that was the case/you'd be left with constant bootloop)
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
MistahBungle said:
I know you've mentioned what's on the sticker on the phone chassis under the battery but are you absolutely 100% sure it's an I9100 ?
Click to expand...
Click to collapse
At the top of the download mode screen it says "PRODUCT NAME: GT-i9100". I don't know any other way to tell besides this and the sticker on the back. There are no carrier markings anywhere, and this phone was purchased because it had an FM radio, which only the international version had.
And assuming by "Hopper's thread" you mean this one, I can't because the files are no longer available.
In that case, you're stuck with the other suggestions to try in his thread & continuing to flash stock roms until you get a properly successful flash I.E phone boots/works normally. There might be something really obvious here being missed, but because we're not there with you/don't have the phone in front of us it might be difficult to work out.
It's working!
Yay, I got it to work! I flashed a custom kernel (jeboo), which allowed me to get into CWM. From there I sideloaded CM10 and now it's up and running! Only I still have a problem with internal storage... (That was the problem I was trying to fix originally.) Would the next thing to try to fix that be flashing a PIT file? If so, any tips for doing that?
I'm going to put off trying to fix that problem and do it when I get back. For now it works as a phone, and that's what's most important to her anyway. Thanks for your help MistahBungle.
Solved!
For anyone else who comes across this thread, I was able to solve my problem permanently by flashing a new PIT file. I found the correct PIT files for the GT-i9100 in this XDA thread. It seemed my partitions had become messed up long ago, as the phone had been showing a 2GB /data partition and only a 2GB internal SD card partition (which should've been closer to 12GB) for some time.
I choose a 4GB data partition (since I was running low on /data space last time). Oddly enough, booting the stock ROM after flashing the PIT only showed a 2GB data partition. Once I flashed CM10 it showed as 4GB though.