I have a GS 2 I777 on AT&T that ran 4.0.4 with the latest update from AT&T. I used Odin to install Siyah version 3.4.2 and since i have, the phone is in an infinite loop when booting. I get the first screen with the yellow warning icon and the device name, then it goes to the siyah kernel logo, and then back to the device name screen. This repeats over and over.
I've tried putting different versions of Siyah back on the device: 3.2.6 and 5.0.1, but none work and leaving the battery out for 15 minutes
What can I do to fix this?
By moving this thread to your forum
Ask a mod to take it over there.
Sent from the little guy
tatesn said:
I have a GS 2 I777 on AT&T that ran 4.0.4 with the latest update from AT&T. I used Odin to install Siyah version 3.4.2 and since i have, the phone is in an infinite loop when booting. I get the first screen with the yellow warning icon and the device name, then it goes to the siyah kernel logo, and then back to the device name screen. This repeats over and over.
I've tried putting different versions of Siyah back on the device: 3.2.6 and 5.0.1, but none work and leaving the battery out for 15 minutes
What can I do to fix this?
Click to expand...
Click to collapse
1)u are in the first place on a wrong thread (meant for I9100).
2)And foolish enough to flash a kernel meant for I9100 on ur I777 phone (which is quite Different hardware wise compared to I9100).
3)U should feel lucky that ur phone is still ON.
4) Visit www.sammobile.com and download a stock firmware meant for ur I777 AT & T version.
5)flash the same from ODIN to get rid of the mess.
6)Finally put some sanity into ur brains and Do some reading before doing anything silly
Good Luck!
Sun90 said:
1)u are in the first place on a wrong thread (meant for I9100).
2)And foolish enough to flash a kernel meant for I9100 on ur I777 phone (which is quite Different hardware wise compared to I9100).
3)U should feel lucky that ur phone is still ON.
4) Visit www.sammobile.com and download a stock firmware meant for ur I777 AT & T version.
5)flash the same from ODIN to get rid of the mess.
6)Finally put some sanity into ur brains and Do some reading before doing anything silly
Good Luck!
Click to expand...
Click to collapse
That's not true those two phones are extremely similar hardware wise.
Sent from my HTC One using Tapatalk 4 Beta
tatesn said:
I have a GS 2 I777 on AT&T that ran 4.0.4 with the latest update from AT&T. I used Odin to install Siyah version 3.4.2 and since i have, the phone is in an infinite loop when booting. I get the first screen with the yellow warning icon and the device name, then it goes to the siyah kernel logo, and then back to the device name screen. This repeats over and over.
I've tried putting different versions of Siyah back on the device: 3.2.6 and 5.0.1, but none work and leaving the battery out for 15 minutes
What can I do to fix this?
Click to expand...
Click to collapse
You may be able to fix it by flashing a version of siyah or another similar kernel which is compiled specifically for the SGH-I777. If that doesn't work, then as someone stated, you should flash back to stock, or stock plus root if you plan to modify the firmware. See the links in my signature for more information, and after you have read, feel free to ask any questions here.
creepyncrawly said:
You may be able to fix it by flashing a version of siyah or another similar kernel which is compiled specifically for the SGH-I777. If that doesn't work, then as someone stated, you should flash back to stock, or stock plus root if you plan to modify the firmware. See the links in my signature for more information, and after you have read, feel free to ask any questions here.
Click to expand...
Click to collapse
That did it, thanks! I following the links in your signature.
Related
I have a few questions about updating my phone to ICS roms,
Current setup,
CWM 5.0.2.3
Rom: serendipity 8.1
Rooted: yes
kernel: unsure
Desired setup
siyah kernel v3.2.7.2
mod: Pure ICS v7.5
CWM 5.5??
Questions
1. do I need CWM 5.5 to install Siyah?
2. What order should I install everything or does it matter.
Sry for the noob questions I just dont want to brick my phone :laugh:
thanks in advance for the help.
I think that CWM 5.5 comes with Siyah already. I'm not 100% sure. And it doesn't really matter which version of CWM you have, they all work the same way.
First, flash the ROM and then flash Siyah (so you need to download the CWM version).
Ok so Installed Pure and Siyah
BUT, now my phone is forking slow, and it keeps telling me things have crashed such as com.google. and Exchange service. I must have messed somthing up but i cant figure out what
It seems upon further inspection that i really messed up, I am getting a new rom to try and fix things, the rom i have on my phone right now will not do ANYTHING, ill update when i get somthing figured out so others can avoid my mistakes.
Ok so i got Omega Series v15
installed and working....sort of, on the bottom of the phone the menu button works like a back button, the back button and search button both do nothing.
also the screen will dim but never black out on its own. So i still have things to figure out
weaponzero said:
Ok so i got Omega Series v15
installed and working....sort of, on the bottom of the phone the menu button works like a back button, the back button and search button both do nothing.
also the screen will dim but never black out on its own. So i still have things to figure out
Click to expand...
Click to collapse
You sure you have an I9100? The I9100 doesn't have a search button.
Sounds like maybe you have might have one of the US variants...
Check the label under your battery.
If the model number says:
SGH-i777, go here.
SPH-D710, go here.
SGH-T989, go here.
If it doesn't say any of those three, plug the model number it DOES say into google, followed by "site:forum.xda-developers.com" to find the forum for your device.
EDIT: a quick google of "Serendipity 8.1" reveals this as a ROM for the AT&T Galaxy S II, which is the SGH-i777. Follow the i777 link above.
Hi,
Yes I'm noob, yes tried searching and saw a similar thread though the phone model is different.
I tried to root Galaxy S2 i9100 in Gingerbread (2.3.6 I believe) from Bell Canada for my cousin using the method from (oh I hope this forum is okay with outside links) galaxys2root.com
Launched ODIN 1.85 and clicked PDA with file "CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5.tar"
Saw the COM box highlighted in yellow before doing anything.
Clicked start and everything was ok saying everything was successful.
So the phone rebooted showing me a the logo screen and a yellow triangle only to give me a blank screen afterwards.
I can still go into Download mode try rooting again, I already have 4 attempts logged into the phone.
Is the phone just soft-bricked or is it un-salvageable? It already has a big crack running though the home button so I'd guess so
All helpful posts are appreciated!
You've used the wrong kernel. You've used an ICS kernel on GB.
Find the correct kernel here.
You should have made sure you had the right kernel to start with. Just knowing it's 2.3.6 isn't enough (and tbh you don't seem too sure about that). You can't just flash any kernel to any firmware. You might need to flash a new firmware just to be sure which one you have now.
If you flash an ICS firmware you can clear the triangle and the custom binary counter with triangle away.
Yeah I was actually looking around for the triangle issue and DL'ed Traingle Away from another thread in the forum.
How am I to find my kernel version if the phone won't get past the logo screen?
Thanks again for the response.
go into dl mode and flash a gb kernel to go with your gb rom.
postfatal said:
go into dl mode and flash a gb kernel to go with your gb rom.
Click to expand...
Click to collapse
Ok looking at Chainfire's 8th post I see kernels for GB. Would it matter to which one I choose?
Well that was easy, I used CF-Root-SGS2_XW_INU_KL1-v5.0-CWM5.zip in Odin and everything is back in order.
Thanks guys, I appreciate it alot. Then again this has to be a noob mistake :0
Hi all,
I have had my S3 since July '12 and in true Android style rooted it and started flashing ROM's left right and centre. Eventually I stuck on Omega, mainly because I got bored of continually flashing a ROM, installing my fave apps, restoring backups from Titanium, setting up my settings etc...
Christmas eve came and, having some time off work, I decided to start flashing some new ROM's...
Jump forward a few hours.... Tried CM10... liked it but wanted more of the Google/stock bits and pieces back so went to flash another ROM off XDA.
All of a sudden the phone goes off. Phone hard bricked. Wouldn't turn on, wouldn't charge... I shat myself.
I got a little brave and RMA'd to Samsung hoping that if its hard bricked they'll just swap the system board or whatever, and thankfully, a few weeks later and I have my phone back. Yay me!
First thing phone does when I connect to my home Wifi, OTA. Only a small update, and wasn't really paying attention as I was still setting up the phone.
Left it stock for a week and then decided I needed root. Rooted phone using the Samsung S3 all in on toolkit v7 from the XDA boards. All well.
So now I'm a little gun shy of flashing my phone, especially after reading a note in Christiano Matos' ROM thread for crDroid v11 about flashing various Bootloaders; and admittedly not properly understanding it as it seems a little Google-translate jumbled up.
Also http://crave.cnet.co.uk/mobiles/samsung-galaxy-s3-sudden-death-security-flaw-fixed-in-uk-50010094/ makes me a little nervous...
Is the 'hard brick' a hardware fault (and as such I wouldn't link it to any software or ROM I installed and something I'd hope my replacement phone wouldn't suffer twice) or a software issue that can be exploited (in which case which update is it that fixes it and do all decent ROM's include this update)?
And finally, what ROM do people suggest? I want to get rid of the Samsung bloat and have a nice speedy UI with plenty of battery life.
(ignore the FoxHound banner in my sig!!)
Post from crDroid thread:
Quote:
- SAMSUNG APPARENTLY SUDDEN DEATH PREVENT: AS YOU GUYS KNOW SOME S3 I9300 IS SUFFERING WITH A WEIRD BUG THAT SIMPLY ENDS IN SUDDEN DEATH .
USE WITH LAST STOCK, PERSEUS, BOEFFLA OR YANK55.LU KERNELS AND PHILZ RECOVERY.
THIS LATEST FIRMWARE XXELLA COMES WITH NEW BOOTLOADER APPARENTLY THAT FIX THIS BUG. THE BAD NEWS IS: THIS BOOTLOADER CAN ONLY BE INSTALLED THROUGH ODIN PACKAGE. BUT WE DON'T WANT THIS, RIGHT?
FLASHING THIS BOOTLOADER BECOME UNABLE TO GET BACK TO THE OLD ONE. BINARY COUNTER CAN'T BE RESETED (STAY ALWAYS WITH 1 COUNT).
HERE IS A LINK WITH BOOTLOADER FILES. ONLY FLASH IT WITH ODIN PC AND PUT IN PDA FIELD.
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
You don't really need to flash any new bootloaders etc. because if it breaks like it did before,you know what's going to happen - Samsung will fix your phone, and that's it.
If you don't like the stock Samsung firmware, try CM10.1. Read about bugs etc. before you start crying about things not working though, because it still isn't, and most probably never will be 100% stable.
bortak said:
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
Click to expand...
Click to collapse
Exactly what I thought, until I hardbricked my cousins S2 on the weekend. Never ever thought it could happen. Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Sticky from the S2 forum:
http://forum.xda-developers.com/showthread.php?p=36947154
Anyway, this is the last thing I wanted to hear. Fingers crossed it was just a one off and not actually related to flashing.
Sent from my GT-I9300 using xda premium
well, basically if you don't touch BOOTLOADER staff , it should be highly unlikely to brick devices , except in the case they released problematic firmware as once i bricked my Nexus S with problematic bootloader released by Google... damn it ...
only thing concerns me about S3 is SDS , but i have installed patched recovery and kernel i think i can breath a little easier now ... but still don't like taking ticking bomb around my pocket... it really sucks...
Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Click to expand...
Click to collapse
You are referring to the brickbug in _leaked_ firmware builds. All official releases by Samsung are not affected.
Also the bug is not only triggered by CWM but by every major operation when a kernel with the MMC_CAP_ERASE flag set.
but still don't like taking ticking bomb around my pocket... it really sucks...
Click to expand...
Click to collapse
Afaik the problem was related to a ****-up in the SSD's wear leveling - so if it is fixed it is fixed =)
Btw, just because it is _now_ impossible to reset the flash counter does not mean it will never be. Samsung does not use eFuse's so there is always a hidden switch that can be reset =)
For CM10 - I never expected the full functionality that Samsung's own firmware had, or at least not the polish and extra apps that are bundled but to be honest, I can live without SVoice, kies etc.
I have read the thread on SDS and have checked my phone with eMMC check (and also advised three others who I work with to check their S3's too), and I have also updated recovery (TWRP) to latest version so I should have some protection... shouldnt I?
I think I will stick with stock for now, see what comes in the future, and what Samsung release through OTA etc. (BTW phone was bought outright by me so is UK Unlocked, no branding).
Dear @OP.
Feel free to answer all your questions by yourself. I'd recommend you to stop being lazy, move your ass and read a few things, starting from here as it triggered your attention.
Furthermore, personally I would recommend you to read carefully this to avoid your threads being locked.
In relation to above, I'd like to recommend you visiting this section of XDA Froums, if you want to use something customized. If not, feel free to use this top secret trick to find Stock ROMS here on XDA....
Wow! Who knew! Consider me put in my place... [edit]
Now I will go and beat myself with a wet towel tied in a knot at the end.
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Thanks for that Cooza; one thing there I didn't know; you can flash a 3rd party kernel to a stock firmware.
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Kind sir,you can reset the counter on the new bootloader as long as you are running stock kernel and stock recovery! last night i flashed trough modile odin the stock kernel and the stock recovery over philz recovery ,and after i used triangle away without any problems!
bottom line short,with the new bootloader you cannot reset the counter while you are runing custom kernel and/or custom recovery!
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...
Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Kari458 said:
Hey.
I've been working recently with my brother's AT&T i777 Samsung Galaxy S2. I couldn't root it at first, then i found the note that i777 does not have the bootloader lock, and then i proceeded with installation of CM stable version, step by stop, according to this page:
Install_CM_for_i777 (cannot post links)
So...i downloaded file, renamed it and placed it in my Galaxy S2 internal memory (the same folder where i put files to my Galaxy Nexus).
Phone does not have stock recovery, so i thought about flashing it via Odin after changing file format in Total Commander.
Anyway, i took out battery, placed it in again and...BANG! Phone only boots while on charger or USB cable. I am able to get it into Download mode. That's why i tried to repair it using almost all firmwares (via Odin 1.85), i used Siyah kernel to get it right, and i even flashed the proper bootloader to make it move. On the way, i also flashed some i777 firmwares that were already rooted. No results.
IT ONLY SHOWS THE EMPTY BATTERY SCREEN, FLASHES, AND BACK AGAIN. LOOP.
I would reallly, Reallllly appriciate help.
Thanks!
Click to expand...
Click to collapse
Yup
cyril279 said:
You've mentioned a lot in your post, some of which isn't very clear to me, so I'm going to ask a few questions in an effort to fully understand where you are. (I'm less worried about how you got there).
The immediate goal will be to get your pone booting into the stock samsung distribution.
We'll cover rooting and custom firmware later.
You are able to get into boot mode (that's a good sign), but are you flashing the stock UCMD8 firmware via desktop Odin?
If no, then flash the stock UCMD8 firmware (see sig)
If yes, when the flash is complete, does the screen show the result: pass?
-Cyril
Click to expand...
Click to collapse
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
I've raged on this device a time or three myself, I promise.
The most abnormal part of each of your posts is the battery involvement. You shouldn't have to touch the battery at all for recovery mode, download mode, or flashing, so I would guess that you're up against dirty or failing charge port, a near-dead or failing OEM battery, or similar issue which made your flashing journey more troublesome than it should have been.
There are several posts [like this one] about troubles using i9100 batteries. They fit and function, but exhibit undesirable charging issues, which consequently tend to get blamed on some other aspect of the device.
The symptoms of a dirty or failing charge port also commonly mis-direct users to blame firmware, batteries, and everything-else.
-Cyril
Kari458 said:
Thank you for your answer and concern Cyril. But i don't know how (i'm still wondering why) i managed to get it right. In rage, i pushed the battery from the model i9100 (GSM Galaxy S2) and....it BOOTED! The rom and kernel was not right so i flashed already rooted version of firmware 2.3.6 and from that step, when i noticed i had superuser, i installed CM 10.2 stable ROM. During the process of installation of CM 10.2 i had to switch batteries (at most 3 times change battery in order to push phone to recovery and escape bootloop during installation of gapps). Now the phone works well with both batteries and is safe and sound. BUT STILL!!! I wonder why it reacted on the battery from i9100 model? Why this was the factor the phone needed to procede with further modifications? Any ideas? Feed my curiousity, lol.
Charlie
Click to expand...
Click to collapse