Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
Boot loop on I19300
Hey,
I have recently purchased a brand new Samsung Galaxy S3 (the international version). It was very impressive, as it was my first smartphone.
Anyways, I googled some and found out that you can change the ROM that your phone is working on, so I went ahead and, read some tutorials and watched some videos. I flashed MIUI version 2.10.19 (the US version). I can't remember if i rooted the phone before or after i flashed the miui rom though. After a few days i got bored. The phone was slower and the battery consumption was worse than the basic ROM. So I went ahead and downloaded the stock polish ROM for jelly bean (4.1.1), and flashed it. The phone restarted and then it was stuck for several long minutes (8-9 minutes) on the flashing samsung logo. As far as I know, that is what a boot loop is.
TL;DR - flashed MIUI 2.10.19(US), rooted the phone, flashed Polish rom 4.1.1 now stuck on boot loop.
Thanks in advance, sorry for the long first post.
Is your phone the US version (2Gb, dual core, LTE) or the international version (1Gb, quad-core, 3G) ???
You should have flashed the ROM specific to your model, since the US and Int'l versions are very different. Since the MUIU for US worked, I guess you have the US model, therefore the Polish version (Int'l) will NOT work for you.
If damage is done, try booting in download mode and flash the proper ROM using Odin3.
Afterwards, boot in recovery and wipe Dalvik + Data and see how it goes.
Hi,
Today I flashed my galaxy S3 to android 4.1.1, I already had jelly bean but the Poland firmware release. I re-installed the firmware but the UK version from SamMobile (Stock Version, Released On The 23/October) [Can't Post Links Untill 10 Posts] .
After flashing the firmware my phone won't seem to go past the Samsung boot screen, I have rebooted, battery pulled and also re-flashed the same UK 4.1.1 firmware but I still come across the same issue. I then played around with the phone wiping all its data and doing a factory reset, I then decide to flash back to the older jelly bean I was running (Poland) and it now boots up and displays a sense UI problem, I cant make calls and access a lot of other features like notification bar and app manager.
TL;DR: I Found The Problem, I Flashed My S3 By Clicking On Phone In ODIN And Not PDA :/ Is There Anything Else I Need To Do Since I Did Flash With Phone At First, Everything Seems Fine Now?
Any Ideas?
Thanks,
Simon
Go to download mode
flash again
Hi,
In my ignorance I loaded on the i9100 rom from Samfirmware XXLSJ, and it loaded ok. However the modem doesn't work. The symptoms are: connects ok to 3g network, however will not txt/make phone calls, the phone reports "not registered on network"
So, I tried flashing the XXLSJ JB again, this time with another modem, one that is supposed to be for the T variant, I'm in New Zealand by the way and use Telecom. Same deal.
No problem i thought, ill simply go back to an earlier official Telecom version on ICS. However, this now hangs on boot up on the S logo.I went back to an earlier one, that one also hangs. I went back to Gingerbread, that hangs on start up also on the S logo too.
So some questions:
Can i run jellybean and use some new modem?
If not, can i put it back to original 4.0.3 official firmware without it hanging?
I'm using Odin 3.07 to do the flashing.
Thanks in advance, i'll just be happy with a working phone at this stage :silly:
laserfist3000 said:
Hi,
In my ignorance I loaded on the i9100 rom from Samfirmware XXLSJ, and it loaded ok. However the modem doesn't work. The symptoms are: connects ok to 3g network, however will not txt/make phone calls, the phone reports "not registered on network"
So, I tried flashing the XXLSJ JB again, this time with another modem, one that is supposed to be for the T variant, I'm in New Zealand by the way and use Telecom. Same deal.
No problem i thought, ill simply go back to an earlier official Telecom version on ICS. However, this now hangs on boot up on the S logo.I went back to an earlier one, that one also hangs. I went back to Gingerbread, that hangs on start up also on the S logo too.
So some questions:
Can i run jellybean and use some new modem?
If not, can i put it back to original 4.0.3 official firmware without it hanging?
I'm using Odin 3.07 to do the flashing.
Thanks in advance, i'll just be happy with a working phone at this stage :silly:
Click to expand...
Click to collapse
Sorted, ran the old firmware back on from Telecom, went into recovery mode and did a factory reset. all seems better.
hie guys recently i tried to install a custom rom (jelly bean 4.2.2) on my galaxy mega i9200 this was due to the fact that it was showing an error written set warant bit kernel so i read a thread on this forum that said once there is such an error reinstall custom rom after the successful install with odin 3.0.7 the phone just starts up and writes.
Image size too large !! W:1080 H:1920
display image fail
Secure FAIL: KERNEL
When i try to charge the phone it keeps on vibrating and switching off without showing the battery that its supposed to show when charging . i have a video showing the error , i uploaded it on youtube here is the link ( h.t.t.p.s://w.w.w.youtube.co..m/watch?v=YuXfEHvOESQ ) just remove the extra dots since i am still new to this forum i am not allowed to post links .
Please guys can you help me fix this error.
please guys help me i am desperate here please its my only phone.
At first try to install stock ROM from Sammobile but bear in mind which version of Android do you want. You can flash 4.2 or you can install newest 4.4 (if you want close encounter with KNOX).
trurl3 said:
At first try to install stock ROM from Sammobile but bear in mind which version of Android do you want. You can flash 4.2 or you can install newest 4.4 (if you want close encounter with KNOX).
Click to expand...
Click to collapse
Firstly thanks to trul3 for your help .
Ok problem fixed after i downloaded android 4.4.2 from sammobile and installed it with odin 3.07 but it did not boot into the system whilst it had kitkat installed , it kept on having a boot loop on the samsung logo so i decided to downgrade it to stock rom 4.2.2 and it worked the image size problem was fixed but now there is no signal , no bluetooth , no wifi , no ime , no sound also doesnt record either video or audio and it says set warant bit kernel on startup .
Anyone please help me solve this new problem now.
And that's why I warned about to be sure what version of Android you want - from 4.4 there is NOT way back to 4.2 without problems... KitKat have new version of bootloader and is NOT downgradable... at least without serious problems, soft brick included. Now I do not know what to do - imao you can try to download (once more) stock ROM 4.4 and to try flash it using Odin... but lack of IMEI is sign of possible massive damage of internal partition configuration. It is important to know which wersion of Android did you have BEFORE installing custom ROM first time, that means what was your LAST stock ROM?
There is another possibility - you can try to install MegaFire ROM from @meglomanic14 which is in fact stock 4.2 rom but greately improved. This can be safely installed even on 4.4 rom's. The link to thread you can find in my sig. But bear in mind, so it is rom for I9205 so if you greatly value FMRadio in your phone, you shout forget about it - I9205 is LTE version vithout FM Radio. There is either 4.4 version of megalomanic14 rom - MegaKat, but it required special manner of instalation.
ok i wanna try to install megafire , the radio is not important to me i can do without it can you tell me how i can go about it.
solved problem
After trying so many different methods to fix my phone i finally got a way to fix the problem and now i will give the solution in order for someone who has the same problem to be able to fix it .
At first i tried updating my galaxy mega i9200 to 4.4 kitkat using O.T.A but after installation the phone started to have a boot loop so i decided to root the device which ended up causing my warrant to become void now my phone starts up with a message written in yellow written set warrant bit kernel , i tried to downgrade it back to its stock rom 4.2.2 but upon installation using odin 3.0.7 i installed the wrong country firmware which resulted in my device having errors written image size too large ....... after this i tried installing megakat 22v but still it didn't work it only started to freeze on the Samsung logo . I later on used Samsung kies to help me find the country which my device firmware was made from , the steps are as follows on Samsung kies go to tool/firmware upgrade and initialization/model (type GT-I9200)/serial number (type -------)/..
After i got my original firmware which was Thailand *(THL) i tried to install with odin 3.0.7 but it failed so kept on trying different firmwares until the one from Egypt worked but when it booted there was no sound , no Bluetooth , couldn't recording sound or video no WiFi and ime was null/null so i decided to download kitkat from the firmware manufacturer Thailand (THL) from androidxda but this time instead of installing the kitkat i opened the I9200XXUCNC2_I9200OLBCNC1_I9200XXUCNC2_HOME.tar .md5 file with 7zip and extracted a file called NON-HLOS.bin its 49.5mb in size this is a file that contains the modems of the phone and other files required for sound and ime , so i put my phone in download mode and opened odin 3.0.9 . I loaded the NON-HLOS.bin file into odin through CP and i hit start after the install the phone was perfect everything worked fine the ime is restored and all is well .
Thank you all who had suggestions on how i could fix this problem .:victory:
Gosh you did all this ridiculous nonsense when you could've fixed your bootloop on your initial 4.4 install by just booting into stock recovery and doing a factory reset.
the factory reset did not work i tried it whilst i had restored the phone to custom rom , it still had the same problem thats why i used that "ridiculous method " .
Man plzz i need the link for the kitkat
dvix said:
the factory reset did not work i tried it whilst i had restored the phone to custom rom , it still had the same problem thats why i used that "ridiculous method " .
Click to expand...
Click to collapse
... I'm facing the same problem help i need the link
abouddweiri said:
... I'm facing the same problem help i need the link
Click to expand...
Click to collapse
You would be best off just reflashing stock ROM in Odin