After rooting my S2, I tried to flash this rom: http://forum.xda-developers.com/showthread.php?t=1576906
but then on boot up, I got the yellow triangle boot-loop issue. Now, I'm a grade-a lurker and I know to search for these problems and I never had to open my own topic, but I've literally dug everywhere and tried every resolve I could find but I can't for the life of me find something that works.
I have tried flashing with Odin3, I have flashed a PDA to the stock kernel. This did remove the yellow triangle, however I was still stuck at the Samsung Galaxy SII screen.
So then I read another topic saying to flash another PDA ontop of that one, so I did. I did do a wipe before in Recovery mode, but it still did not get me passed the title screen.
I have waited at the screen for a bit too, yet nothing.
I have used Odin with several other stocks, but nothing is getting me anywhere. I have searched many threads and I have tried everything, but I'm getting hopeless. Like I said, I don't normally post anything but nothing I've found so far has helped me so this is a last resort
So basically: Yellow triangle, followed popular guides (http://forum.xda-developers.com/showpost.php?p=18608050&postcount=6) and many variations of that guide, still nothing.
Sorry for being a newb but any help and efforts would be EXTREMELY appreciated. If any additional information can aid in a solution please let me know.
Did you try the return to stock thread? Stickys?
http://forum.xda-developers.com/showthread.php?t=1511838
It sounds like you flashed a CRT off animation for ICS for the International version of the S2 I9100. (first link in your post) This may have flashed something not intended for the I777. You do have an AT&T version of the Galaxy S2, I777 don't you?
Edit: you flashed a framework-res.apk that doesn't work with your phone. You should recover by flashing back to stock.
full return-to-stock followed by recovery wipe
It's always better to post to an existing related thread than to start a new one.
We already have several threads that cover this.
Thread closed.
Related
Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Rareutu said:
Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Click to expand...
Click to collapse
Have you tried using Odin to go back to JFD? with re partitioning checked?
Tried JK2?
The splash screen is usually controlled by the kernel, you could also just try re flashing a stock vibrant kernel to see if that works.
I'm having the same issue. Just got a used Vibrant yesterday and I'm not sure what version it was on. I downloaded a bunch of apps and all was well - it worked great. I went to bed and when I woke up this morning it was stuck on the Samsung Vibrant screen. I tried using Odin with the 512.pit and the JFD.tar but that did nothing. I then found a one-click fix, not realizing it was only for the Captivate and used it. So now my T-Mobile Vibrant is stuck on the AT&T World Phone screen.
I can get into Download mode just fine and I have re-loaded the JFD in Odin several times, including doing so with the re-partition box checked but to no avail. I'm downloading the JKT rom now, though I have little hope that that will do the trick after all I've already done.
Any suggestions?
PS - I also tried downloading the All_In_One.zip and flashing to the Original.tar, then the T959UVJI6.tar. No dice. Nothing seems to work.
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 was trying to install the JB update using Odin but I kept getting all kinds of errors (mostly the NAND read write fail) and eventually the *update failed* yellow icon recovery mode. after endless hours of browsing and reading up on the internet, I tried installing the Clockwork recovery which *yaay* worked. so, I went on ahead and got the Slimbean ROM and installed that via Clockwork. installed fine but wouldn't boot, just got stuck at the Slimbean logo. thinking that perhaps the ROM was wrong, I got the CM 10.1 but that got stuck too. where am I getting it wrong?? any help would be really appreciated
P.S
I did not put android debugging on as I thought that since I would be installing stock firmware, that it isnt really needed.
the phone was previously on GB, never rooted or toyed with before,
I have tried deleting dalvik cache/ data wipe and factory reset
& it's the i9001gt variant.
Before we go anywhere, is it actually an i9001? Or i9100?
If it's i9001, then you're in the wrong forum.
If it's an i9100, try flashing hawkerpaul's ROMNuke script, then immediately flash Slim/CM.
Sent from a galaxy far, far away
Still Stuck
Hopper8 said:
Before we go anywhere, is it actually an i9001? Or i9100?
If it's i9001, then you're in the wrong forum.
If it's an i9100, try flashing hawkerpaul's ROMNuke script, then immediately flash Slim/CM.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
its the i9100g. thought I'd post here since there's no 19100g help forum. I did try the ROMNuke script for the i9100 as I couldn't find a i9100g version and it seems to flash ok, but am still stuck at logo on both CM and Slim.
one thing I should mention, I used the PIT file that comes with Odin and chose repartition (whew!) at the very beginning of trying to flash the phone before I knew what PIT files are. could that have somehow messed things up?
I'm sorry, but I really don't know much about the i9100g. I don't know if cleaning scripts are compatible, or if that's adversely affected anything. To get the best help, post in the i9100g Q&A. Its stickied at the top of the i9100g android development section.
Sent from a galaxy far, far away
No introductions here, just want to get straight to business... I don't mean to sound so impulsive but I've just been so annoyed by this and I just want a working phone again. I am running Stock Jelly Bean 4.1.2 on the carrier Vodafone (I have not rooted my phone). I have looked around the forums for answers but all of them don't seem to work for me.
This all started over a month ago when I was on Youtube and suddenly the touchscreen froze (the video was still playing) and the buttons were unresponsive. I pulled the battery out and put it back in after a few seconds. When I turned it back on it came to the 'Samsung' animation again and again (a boot loop).
Not knowing that the best option here want to go into recovery and do a factory reset, I went to recovery mode and wiped the cache partition. I rebooted the phone. But this time I was stuck on the 'Samsung Galaxy S2 GT-I9100' screen. I also found out that my recovery mode was not working. It would just have the android robot with a sphere in the middle for ages then it would reboot into the 'GT-I9100' screen. My download mode however, is still functional to this day.
As I've been told, as long as you have access to download mode, there is still hope for recovering your phone and putting it back to normal. So far I have tried:
Installing multiple stock JB ROM's such as the ROM's with LSW and MS2 on the end of the file. I have tried two versions of Odin (1.35 and 3.07) but with no results. The downloads of the ROM were no problem.The flash would be OK up until 'cache.img'. The flash would then freeze then proceed to say a big red 'FAIL'. Note that I have tried to do this on multiple computers while using different USB ports (mainport with no USB hub) for each flash. I have Kies installed but have killed all the processes and opened Odin as an administrator. I have used the original S2 cable that came with my phone and one other data cable, but still no results. I refuse to flash any PIT files because I don't like the risk associated with them. I have yet to flash these firmwares:
LSJ (JB leak), LSD, LSS, LS8, MS7
The drivers might be the problem so I might reinstall them but I don't know how...
Yesterday, I was told by a friend that he had the same problem before and all he did to simply fix this was to download the S2 Jeboo custom kernel (which has CMW with it). He also said rooting the phone would also fix it. I have attempted to flash said kernel with Odin 1.35 when it got stuck when the green bar was full. I pulled out the battery and the USB, put the battery back in and the USB (in a different port) and attempted to flash again. Nothing. I notice now that there is a yellow triangle below the 'GT-I9100' screen when I attempt to boot the phone and that my custom binary count has increased to 2. When I attempt to go into recovery mode the screen flashes twice and just stays in the 'GT-I9100' screen instead of the android robot from earlier.
That's it really. I hope someone can help me in this almost hopeless situation... I have typed about this before on another forum but I had no replies that would help me. I could go to a service centre but my warranty's gone and the yellow triangle might cause some problems. The information from xda-developers has always been solid and reliable... so can someone help me out
Same as everyone else in this situation - find Hopper8's 'Odin troubleshooting' thread stickied in General, and go through the troubleshooting steps in a methodical manner until you get a successful stock flash, as this is the only way you're fixing it.
In your situation/given what you've already tried, I would be downloading the 3 part firmware (the 'leak' you referred to) linked to in the thread & flashing that first, which will wipe your phone & hopefully remove any remnants of what was previously on the phone which may be tripping you up.
This may not be successful first time, your flash may still barf as the one's you've tried so far have; in this case it's a matter of going through as many of the suggestions in the thread as many times as you need to until you meet success (including multiple PCs if necessary). When these are recoverable (and most are), they're often fixed by perseverance.
That thread is 'the bible' in these situations, and there isn't anything else which isn't in the thread that can be suggested in these situations, so you really do need to try absolutely every thing in that thread if you want your phone fixed.
MistahBungle said:
Same as everyone else in this situation - find Hopper8's 'Odin troubleshooting' thread stickied in General, and go through the troubleshooting steps in a methodical manner until you get a successful stock flash, as this is the only way you're fixing it.
In your situation/given what you've already tried, I would be downloading the 3 part firmware (the 'leak' you referred to) linked to in the thread & flashing that first, which will wipe your phone & hopefully remove any remnants of what was previously on the phone which may be tripping you up.
This may not be successful first time, your flash may still barf as the one's you've tried so far have; in this case it's a matter of going through as many of the suggestions in the thread as many times as you need to until you meet success (including multiple PCs if necessary). When these are recoverable (and most are), they're often fixed by perseverance.
That thread is 'the bible' in these situations, and there isn't anything else which isn't in the thread that can be suggested in these situations, so you really do need to try absolutely every thing in that thread if you want your phone fixed.
Click to expand...
Click to collapse
Thanks for the quick reply, I will look into the guide in more detail and follow the instructions carefully. In regards to the flashing of the JB leak, will this fix the problem of being unable to access recovery mode? And is there any other firmwares you recommend flashing? I really don't want to wipe my phone, as I'm saving the flash of the JB leak as a last resort.
Given what you've already tried & the information you've provided, if I was in your situation I'd be starting with the leak. But that's up to you. If you don't want to do that, you'll need to go through everything in Hopper's thread methodically; eventually you'll get a successful stock flash (and you may end up having to flash the leak to fix it anyway).
Will the leak fix your problem ? Quite possibly, but possibly not. What it will do (if it works) is take you back to a stock setup, so you'll have access to stock recovery. You may end up with bootloop after the flash even though it's successful; in that case you boot into recovery & do a wipe/factory reset.
So far as what stock firmwares to flash, it doesn't matter; they're all essentially the same. The only important thing is you get a firmware on your phone/working. But if it was me in that situation, I'd be sticking with firmwares released by your carrier (flash one of these after the leak if you go down that path).
There isn't a lot else beyond what I've already told you & I can offer; we have that thread as 'the reference' in these situations, neither I nor anyone else here can offer you anything which isn't in that thread. It's the gold standard & covers this issue from every possible angle.
I've been running in circles now for over 3 hrs. Every website I come across seems to have a different way to solve this problem and none of them have worked. When I saw the guide about how to set up root access on Cnet it looked easy but now its just snowballed into a horrible mess.
But it was stopping at the point where it said Getting PIT. Or something like that. I then looked up the solution online and I saw a forum which said to find a factory PIT file and install it. Trouble is that it didn't get any further the SetUpConnection so it wouldn't have been able to run. The phone now boots to the Samsung logo and then goes to a black screen. So far I've tried the following with no success:
- done a factory recovery after clearing the cache.
- reinstalled the factory recovery itself using a file called International-GT-i9300-StockRecovery using Odin
- attempted to install a PDA file called CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 which claims to be a custom build of the firmware
- attempted to install I9300XXUGNH4.LiteROM.AMBASADII.v4.1 but can't find all of the separate files, just the CSC
I'm now completely out of ideas and desperately need some support from people who are familiar with the firmware and stuff on these phones please. It's a Samsung S3 i9300.
[edit] Now tried replacing the Bootloader and Kernels with stock versions XXEMG5 from kamalmawa on these forums. No change but like the others Odin says everything worked.