• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help with flashing problem

Hey guys,

I just installed VillainRom 2.4.2 on my galaxy s2, and wanted to get rid of that yellow triangle. I followed this procedure -

How to remove yellow triangle on Samsung Galaxy S2 without USB Jig? (Video) -

and flashed with KH3, because that was the nearest to my kernal. Everything was going fine but now the phone is stuck on the galaxy s2 screen with the yellow triangle and i cant do anything?

Can somebody please help me, would be much appreciated! :)

Thanks
 
Just after i used CWM to flash Kernal, and after it rebooted itself. Stays on this everytime i boot it up. I can access the download screen. Should i just start again? to atleast get back into the phone?

thanks
 
There are a few things you could try. I would probably just do a wipe and flash villainrom again. Can you boot into recovery still? (Vol up, home, power at same time)
 
If you can get recovery mode then the only thing you can do is flash via odin with some stock firmware. You cant do a wipe because you cant boot the phone or get into recovery.
 
Just flashed with odin to some stock firmware and im in the middle of reinstalling VillainRom again through CWM recovery. Hopefully itll be alright, will let you know
 
Just seen this now, after flashing!! So just do it the same way that the procedure i put up first says to do it? But do it before Villain?
 
Is this a Bell phone? I had this issue too...some kernels are not compatible, you just have to find the right combination that works.
 
I cant see it here at work (surf control). There is a guide in my sig you can follow, post 2 has the remove triangle guide. Remember to match the Kernel with the firmware you are on now. If you are on KH3 use KH3 if its KG6 use KG6 Kernel etc.
Yes ideally before villain because when you flash villain it uses a different kernel.
 
Thanks Steslatt, i might leave it for the time being because i have villain on already and i tried flashing kh3 with kh3 and then that problem arose!

Thank you!
 
Back
Top Bottom