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
Related
I have a Galaxy S 2, I777 from AT&T. I had been running UnNamed 2.0 for a while. I started messing around with different modem files trying to get my data rate a little higher. When those failed to work, I decided to go back to stock and start from scratch. This is where my trouble begins:
I flashed with ATTGalaxyS2Unroot_SGH-i777.tar using Odin 1.85. I've used that before and all was well. After this flash, I'm stuck in a boot loop. The galaxy s 2 logo just keeps recycling.
I have tried a lot of other items I've found on here in various threads about getting out of a boot loop, but have not been successful. I was able to get to the stock recovery mode, chose to wipe user data and did the "yes I'm sure" option. The phone rebooted and I have not been able to get back to it. When it tries, I get in yellow "deleting cryption meta data" and then the phone reboots.
My last attempt was flashing with i777uckh7-cl503881 full. Odin writes everything, says pass and the phone reboots. After it restarts, it quickly goes through some items:
-- Intalling package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfuly installed package...
-- Copying media files...
successfully copied meida files (yes, media is misspelled on the screen)
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
--Updating application...
Successfully updated application.
--Appling Multi-CSC...(again yes, applying is mispelled on the screen)
installing Multi-CSC
Can't access to '/system/csc/02U/system/'.
Successfully applied multi-CSC
Rebooting.
then I get the boot loop all over again. I am still able to get to download mode using the volume button, and my jig still boots to download mode too, so I think there's still hope, but I don't know what to do next.
Any help would be greatly appreciated.
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Creepyncrawly:
Thank you for your post. I didn't find anything searching for that, but, I downloaded and flashed siyah kernel and was able to get to a recovery mode.
I am now restoring the nandroid backup that I made (luckily I was smart enough to do that) before I started messing with modems and stuff.
We'll see how this goes
you sir are a life saver. I was able to restore the nand backup and boot into the os again.
creepyncrawly said:
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Click to expand...
Click to collapse
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Entropy512 said:
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Click to expand...
Click to collapse
I did not think of that, but it makes sense now. At the time, I figured I would stop and get help before I made it worse. Why I didn't restore to my backup to begin with is beyond me.
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
For those who are experiencing the "Deleting Cryption Meta Data" problem, creepyncrawly is correct, it is difficult to solve, but the following steps seem to solve it reliably:
Download and install the I777UCKH7-CL503881 Stock Binaries from creepyncrawly's download repository. Use heimdall or odin to load the stock binaries. You may need to load the param.lfs and/or the bootloaders. However, it may work without loading these files (and loading the bootloaders can be in the "danger zone")*.
With the stock binaries installed, the device will be in a boot loop, and entering recovery mode will either indicate that the device is installing CSC (unsuccessfully), or indicate that it is "Deleting Cryption Meta Data". In either case, you will be unable to actually access anything in the recovery.
In order to get to a working recovery, load the SGH-I777_ClockworkMod-Recovery_5.0.2.3. You'll need to untar this file to get to the zImage kernel file*.
With the CWM kernel installed, you should be able to actually enter recovery mode by holding down Volume Up + Volume Down + Power until the Samsung logo appears for a second time. Note: In this version of CWM recovery, the home button is the 'select' button and the power button acts as the back button. This is different than most versions of CWM.
Using the recovery run both clear data/factory rest and format sd card (in mounts and storage).
Finally, install the Siyah Kernel, using either heimdall* or CWM.
At this point, the phone should be restored, and you can re-flash the I777UCKH7-CL503881 stock kernel (on any other compatible kernel).
onecoolpilot said:
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
Click to expand...
Click to collapse
You can re-flash any kernel you like.
Thanks everyone who directed me to the steps for solving this problem!
* To load these kernel files, put the phone in ODIN mode by holding down the "Volume Down" button while the phone is connected to USB. Use either the ODIN or Heimdall tool to actually flash the device. See this post for complete instructions on flashing the files.
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Red_81 said:
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Click to expand...
Click to collapse
Is this the "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII that you bought on ebay for cheap, or a different phone?
Do you know the history of this phone? Knowing it can help with troubleshooting.
Did you ever see the "Deleting cryption meta data" error message?
As far as having vulnerability to the eMMC firmware bug, you are safe as long as you don't use the buggy kernel, which is pretty much out of the picture by now.
LOL, you read my other post. It is one and the same. The standard story from the seller. "I gave it to my Brother in Law and now it is like this." He stated it did boot properly before. Liquid indicator checks out (haven't pulled the back off to check the full indicator).
I don't get the "Deleting cryption meta data" but I do get the "multi-csc error". Wiping data doesn't seem to take care of that one.
It's really odd because I can flash ICS roms with no problems, but the GB ones stick at the bootscreen every time. Even CM7 stuck there.
I may have to try to rule out hardware damage at this point
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
creepyncrawly said:
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
Click to expand...
Click to collapse
The one from the repository with bootloaders. I tried the one without bootloaders first, but it did not fix it.
Currently I flashed over to ShoStock2. However, I'm getting alot of problems on that too (Com.android.phone not responding).
I can try to flash back to stock at any moment because I have no data on the phone.
I did try using the latest version of Heimdall, but it kept crashing at 42% (from what I read that is a known bug)
So the one thing you have not tried is flashing PIT? I wouldn't try that next if it was my phone, however, since it is the area I know the least about. There is not a whole lot of information available about using PIT with the I777 (as in nothing I could find).
The behavior of flashing to ICS and running OK but bootlooping on Gingerbread is new to me.
If you have a jig, does the jig boot the phone to download mode?
The phone should be recoverable. If it was mine, I would start by flashing the full stock package with bootloaders and param.lfs again. Then wipe data/factory reset from 3e recovery. Then flash the Gingerbread Siyah kernel. And then wipe data/factory reset from CWM Recovery.
Actually, I thought I typed that before.
I did flash the PIT file at one point out of desperation.
I have a jig that works beautifully (wipes the counter too) and has been a big help through this whole thing. That tells me I should at least have the correct bootloaders.
Do I need to let it attempt to boot between each flash or just go directly one to the other?
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
creepyncrawly said:
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
Click to expand...
Click to collapse
I actually found and tried that a few days ago. Never got that error message before. But I flashed the repair anyway. No change.
I did manage to just let the phone run for a while and all the process error messages went away, but the dialer refuses to start. I also noticed I don't think I'm getting any sound out of the earpiece.
I think I'm going to have to take the back off to check for water damage and to make sure they didn't bleach the dot.
I'll attempt to do some more flashing later tonight if the wife lets me.
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
creepyncrawly said:
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
Click to expand...
Click to collapse
Lol. Under normal circumstances indeed. I appreciate all the help so far. I wonder if there is something borked with the chip.
Sent from my SAMSUNG-SGH-I897 using XDA
Not sure if it helps much since you said you think the correct bootloaders are there but I had the exact same problem as you a couple months back. Like an idiot I flashed the original "one click" ATT ICS leak from Rootzwiki that updated my bootloaders. After this attempting to go back to CM7 resulted in me soft bricking the phone. The ONLY rom that would flash and work was that same ICS one click. Everything else Odin just failed on. Eventually I managed to get the complete stock GB back on it by flashing the full package in creepys guide several times. I gave up on Odin on my pc and had to remove Kies from my Mac so Heimdall would work but it flashed finally and I was saved. If you search through my posts here and find that thread maybe there's something in there that will help cause it sounds like you're having a bootloader issue like I did..
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Thanks. I'll take a look.
On a side note.... I can't get any sound from the device. I'm thinking now that it might be hardware related.
Sent from my SGH-I777 using xda premium
Hello all,
I have tried many things before asking for help, but nothing worked so far.
Here is the story:
I was on ICS 4.0.4, with default ROM coming from carrier.
I wanted to install CM9.1,
spent countless hours doing all backup and reading tutorial.
Tried finally yesterday and it was stuck doing "wiping data". Left it for 20min+ and nothing.
After restarting it, it is now stuck on the boot logo.
I couldn't enter anymore CWM or stock recovery (up+home+power), but could enter Download mode.
So I tried a couple of things I have read on the forum, like installing Siyah-s2-v5.0.1.tar through Odin 3.04 but I still cannot enter recovery mode.
I've read (too late) about the mmc brick bug (couldn't find anyone speaking about it in any tutorial until I reached this point... nothing on CM wiki or in other tuto... classic!).
I hope I'm not in this case though as I can still go to DL mode, and the phones having the brick bug are completely dead (blank screen or no DL mode), as per http://forum.xda-developers.com/showthread.php?t=1756242
I managed to finally get CWM working only by using GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar from Odin, then tried to install CM9.1 from SD card but after reboot it is stuck on the blue cyanogenmod animation boot screen and nothing happens.
Tried also to restore from CWM my nandroid backup, but during the restore it seems to hang then restart by itself, and then I'm back to Galaxy S boot logo (the animated one with the big S).
And after this I have lost again access to recovery mode.
I can't go back to stock and I can't install CM... I was not expecting such issues, it all seemed pretty basic on paper.
I'm really stressed and don't know what to do
Flash a stock rom in Odin (download mode), re-root your phone/flash a kernel with CWM, restore your backup ?
Hi,
thanks for answering,
I have tried to locate such a rom, but I'm not sure which one... is there a specific one to try ? could you point me to it please ?
so far I have tried I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5
but no luck
you also say "re-root", at the time I used this method:
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel - xda-developers
http://forum.xda-developers.com/showthread.php?t=1501719
Do I need root to install Siyah kernel from Odin ?
I'm trying one from sammobile... let's hope :/
The bad thing is I had no Yellow triangle at the beginning since I'm stuck in this boot loop or no boot to be precise.
Now that I have tried different things to fix it, it is still not working and I have my flash counter = 10.
I cannot even go back to the shop, is there a way to reset it knowing I cannot even reach the OS, I have only DL mode or CWM...
Use a stock rom for your region/carrier (or any stock rom from any region really), it doesn't really matter as I presume you'll be restoring a backup and/or going back to a custom rom anyway won't you ?
Samfirmware & AndroidFirmwares.net have lots of stock roms.
No, you don't need root to flash an Odin version of Siyah. So yes, you can flash that after you've got stock up & running to root your phone rather than re-rooting your phone by flashing a CFRoot kernel or using another root method. Just make sure the version of Siyah you're going to flash matches up with the stock rom you've got on (I.E if you flash a GB stock rom use GB Siyah, ICS stock = use ICS Siyah, etc, etc).
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Don't worry about the flash counter. That's the least of your problems while your phone is borked Worry about it when it's fixed. There's nothing you can do about the triangle while your phone is cactus.
When you've got it up & running again, use Triangle Away.
But first things first.
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
You're welcome.
Um, no. Absolutely not. Nothing personal, but if I did that for every person who's asked me for 'hands on' help since I've been here, I'd have spent my time doing nothing else. I don't do 'personal' with people from XDA (which is why I have PM's blocked except for mods).
Besides, you're going to learn much more fixing this yourself. I've given you a stack of information thus far, ball is in your court. Every answer to every question you could possibly ask is on this site. It just sometimes takes a bit of work/reading on your part to find it.
megosu said:
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Click to expand...
Click to collapse
ok I understand.. it is just I have literally spent more than 8 hours on it and had not make any progress at all (even worse I cannot return it to the shop because of the yellow triangle).
I appreciate your help, it gives me a bit of hope but I'm in a very bad situation and I feel I have read and do so much already with no success at all.
I will try your option of restoring the one from Sammobile, I have tried other before without any luck, maybe this one will do... (5min left to DL it).
thanks again for your support
I know where you're coming from. The first flash I tried when I got my phone in 2011 borked because I was careless, and it took me a bit over a day to get the right info/files/etc to get it fixed. I know it's frustrating/tiring/annoying & you're wondering at the start whether you can even fix it. But as long as you've got download mode 99 times out of 100 you can save it.
And as I said, it's good experience; once you've fixed it, you'll be able to handle anything that comes up in future
Let us know how you go. I'm going to bed shortly, but I'm sure someone else will step up & help if you have any further problems.
You're welcome Happy to point you in the right direction.
I have flashed the rom, the exact same one as I had before everything happened...
if it helps, I flashed it from Odin 3.04 as PDA.
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5
I'm now back to the Samsung GALAXY S2 GT-I9100 logo and nothing happens.
I cannot use recovery mode,
I can use DL mode (it shows 11 counts and current binary as Samsung official.)
update:
I left the phone on the first logo for about 5min and it moved to the next Samsung Galaxy S2 logo, with the big animated S.
I'm waiting but nothing else is happening.
I'm still desperate to fix it.
One thing which can be relevant, whenever I try to wipe or format /data from CWM, my phone is restarting after a few minutes or is saying it cannot be done.
I can format /cache and /system.
Could it be the root cause ? Any way of fixing it ?
Thank you
update: I cannot mount /data from CWM, it says Error mounting /data!
is it the brick bug ? :|
Easy now....your device is still good.
Those animations should take like 1-2 mins when you flash a rom.
Now, you are completly sure that you are actually flashing the right ROM for your device model?
If so, just keep flashing stock roms until you're up and running again, so you can start from scrap.
I tried, the issue is as soon as I flash a stock rom (through Odin), then I can't get into stock recovery mode anymore, I have to flash GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar to get back the recovery mode.
I tried to flash several times, I think it is down to the fact I cannot mount or format /data.
Which is why I'm wondering if it is the famous brick bug.
My device is GT-I9100 and I took the stock rom from sammobile:
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 which is ICS 4.0.4 (that I had before trying to move to CM9.1 and having all this mess in my hands.)
flash this:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/.
you are on siyah kernel right?
what you wanna do know is to get to whatever rom your flashing, forget about cmw for now.
this also might help:
http://forum.xda-developers.com/showthread.php?t=1457458
So it is not lost yet ? Not the brick bug ?
just to be sure:
you want me to install through Odin: Siyah-s2-v5.0.1-CWM.zip
then going back to DL mode
I flash through Odin: I9100XXLSJ_I9100OXXLS1_OXX.zip (coming from your link).
anything I'm missing (even if it seems obvious, please let me know as I'm maybe missing something important)
?
I still cannot do Factory reset... is it a problem ?
I dunno what kernel you are using, If stock 4.0.4 kernel you should flash siyah first (safe kernel, no brick bug), and then countinue flashing the ROM. Check out the brick bug thread in general SII forum for directions if you want.
BTW, Odin recognizes your phone right? Check it out, you'll get a huge long breath.
BTW 2: you don't have any kies applications running in your pc.....am I right? if so, CLOSE THEM ALL!
I did had stock 4.0.4 kernel when I first tried to follow CM9.1 wiki, and I did a factory reset through CWM... which is why I think I might have bricked it...
I have checked the brick bug thread (too late it seems...) but so far I can't be sure if I'm in this case or not as they say they can't even reach DL mode, and I can.
Odin recognizes my phone, yes, but anything I flash is stuck on the animated logo.
I do not have Kies installed, just installed the drivers.
Not my first time to root and install a custom rom on other phone, but this phone isn't treating me well.
So I followed the root guides to root the phone.
Downloaded an insecure kernel for i9100. Although, oddly enough, I bought this phone 2nd hand, and when I went to the "about" part for the kernel look up before tried to root it, the kernel info just contained ICS3.?? (forgot) and the date. There was no four or five letter kernel code like I've been seeing. But according to cnet (one of many rooting tutorials), the kernel version doesn't matter as you can change the kernel anytime, or after rooting in this case.
So I installed Kies to get the Samsung drivers installed. Done.
Restarted phone to download mode (volume down, home, power)
Started Odin 3 v1.83
Phone was recognized. Click the 2 boxes (Auto reboot and F. Rest Time).
Clicked PDA, loaded up an insecure kernel.
Status went through OK, ended up with "Pass!"
Phone automatically restarted.
Now the problem. It restarts, shows the Samsung Galaxy S2 logo with the big triangle underneath it, and thats it. Never leaves this screen. I thought maybe it's a kernel problem, so I tried several different insecure kernels, all with no change. I have no idea how to find what kernel was the original one that came with this phone. Would using Odin with the original secure kernel (or even insecure) solve this problem? Otherwise, what else can I do? My note 2 was stolen so I bought this s2 second hand until I can scrape up enough money for a note 2 again, but the damn thing won't even boot up now. :crying:
How can I get this working again, even to have it stock again I'd be fine (though obviously putting on a custom room with root would be best).
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
TheATHEiST said:
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
Click to expand...
Click to collapse
There wasn't much to try, at least as far as my noob self knows about. I tried flashing 6 other kernels I found, merely taking guesses at which might possibly be the Chinese s2 one, I remember from flashing other phones that i had to look for Z or D in the kernel ID. But all of them just led to the same problem of not booting past the logo screen.
Besides just trying to start it up as normal (which doesn't work) and starting it up in download (by holding down vol+home+power), what others ways can I start it up? I don't know how to boot into recovery, and I didn't know I can flash a rom without first rooting it, which I haven't done yet because it's still stuck in start-up.
Searching enough xda threads and just googling seems show a pretty large consensus supporting the existance of a China i9100, plus I see them everywhere (as well as s3, s4, and notes), so I'm 99% sure they are an official and semi-large market for them here (after iPhones unfortunately). But even still, that doesn't help me locate the original kernel.
Under the battery, is says this:
Samsung WCDMA
Model #: GT-I9100
CMIIT ID: 2011CP2751
Do these help? So is any of the steps I did wrong, or can you otherwise point me in the right direction? Appreciate the help.
Don't post your IMEI (or your SN for that matter).
MistahBungle said:
Don't post your IMEI (or your SN for that matter).
Click to expand...
Click to collapse
Thanks for the tip MistahBungle. Edited out.
Hate to say it, but found more help on youtube... Found a guide that walked me through replacing all the files (not just kernel) in Odin that got it back up and running. I'll follow the xda guides again and hopefully it'll work this time... Thanks anyways...
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.
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.