Related
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Teddybear2 said:
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Click to expand...
Click to collapse
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?[/QUOTE
Root Kernel is KG1 from Odia. Happened before with the other Kernel as well. I already cleared cache. There is no insecure KG2 for T-Mobile available. Any idea how to make the Kernel rootable/ insecure. I suspect it must have something to do with the Kernel. For rooting, I try always to get the insecure version of the branded one. Different kernels (insecure/ secure) that do not completely match could cause this?
Maybe I have done something wrong which is the solution. Let's start from scratch how I rooted the phone.
I had original Kernel on the phone. From this one, I upgraded straight to the insecure, rooted and than just put one the most recent one.
Is this causing the problems? So better upgrade to the next official one, than use the insecure to root and than put the official one back on. All done via ODIN? Would this be the solution?
Click to expand...
Click to collapse
I used KIES to get the orginal KERNEL on the phone. So far no problems there. I want to test it over a couple of days and then root it again. Hope this fixed it.
2 Hours later
Okay, after roughly 2 hours I came back in this loop with Internet/ Messages. I cleaned the RAM and now it works fine. Why does this happen? Never had this before. Is this an App causing or just the Kernel. I could use ODIN to get back to the first Kernel that was preinstalled. Phone is currently not rooted. However, when I use ANDROID system Info (App), under BuidlINfo I see Type: USer and USer: Root. Should I probably unroot first as the system is confused and thus these errors appear?
Hope some could help here to clarify.
Need help and advice to fix problem!!!!!
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
Click to expand...
Click to collapse
I always thought power on/off is similar to Reboot. I was proven wrong. I just rebooted with volume up+home+power. Since then phone is stable. Sometimes TWLauncher crashes and reloads.
Thanks for the support. I think this has been fixed....hopefully.
Teddybear2 said:
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
Click to expand...
Click to collapse
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
0semaj0 said:
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
Click to expand...
Click to collapse
Problem was that a system file for synchronisation (syncmldstmo.apk) was deleted. I do not know how, but I could restore it with Titanium. Since then, all my problems seem to have vanished.
My Apps does not work. I do not see any downloaded app. Seems to be a Google problem since I stumbled over several threads.....no solution so far. I asked them directly. No solution.
this is a long story, so bear with me, please:
i used to be on JPKH1 (this was the rom that came out of the box)
i was on XXKI3 when i decided to flash nightly #116 of CM7. i followed the instructions, got it working and had no real issues. however, i felt like CM7 made my phone old-ish (loved it otherwise), so i decided to return to a custom rom. prior to all this, i was on VillainROM 3.0
i flashed XWKJ3, business as usual, and then Batista70 rom. when i did that, something...strange, happened. none of the system functions worked (SNS sync, android system ringtones, etc.). i was overall dissatisfied with it, so i switched to Omega rom 6 XT.
i did that, and installed the relevant version of ICS domination theme by vertumus, and that's when it first happened - both the camera AND android system ringtones were force closing. also, when a system notification came on the unfortunate moment my phone was asleep, there would be a moving pixel on the screen and nothing else until i woke the phone up. nothing i did would fix it, and believe me, i tried EVERYTHING (restore nandroid, fix permissions, reflash rom). at last, i factory reset it, which did the trick but took some of the 'omega' out of 'omega rom'
i flashed stock XWKJ3, factory reset, flashed Omega 7 XT, and the problem persisted. it starts whenever i reboot the phone, for any reason, even if it doesn't change anything on the phone (just a simple power on/power off)
now i was pissed, and went back KI3 and VillainRom 3 and all SEEMED good. there were VRTweaks i wanted to use, but the above DID happen, after all. i rebooted into CWM recovery, took a nandroid, booted up again and sure enough, 'it' happened AGAIN!!!
this has me driving myself crazy, and no one on the Omega thread seems to believe in the existence of my post there (that's how well they're ignoring it). WHAT SHOULD I DO?!!!
by the way, i have NEVER flashed a .PIT file (since i've read in so many places not to touch that thing on the S2) and my binary counter is at a service-center-scaring 7. and for the love of god, don't just read this and go away (that's happened to me before), GIVE ME A HAND!!!
Stock rom via odin, and reroot.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
tried that already
flashed KJ3, then omega 6
flashed KJ3, then omega 6
flashed KJ3, then omega 7
flashed KI3, then villainrom 3.0
or were you implying something else?
Try wiping dalvik/partition/cache before and after installing the custom ROM
I do that out of habit when installing custom roms, as in the above cases
Sent from my GT-I9100 using Tapatalk
Have you tried fixing permissions? Might be worth a try
Sent from my GT-I9100 using Tapatalk
the pixel on the screen is because of app called noLED or something like that just uninstall it like any other apk and your that problem will be solved it automatically installs when you flash OMEGA ROM
@thefaixy: well, solved i guess
@macdam: nope
Sent from my GT-I9100 using Tapatalk
Random but I had an issue on my phone that followed me through different ROMs and kernels like some sort of ghost.
Turned out to be a corrupted video file in my ext SD card which was basically crashing the phone constantly and causing all sorts of strange issues.
Sent from my Optimus 2X using Tapatalk
thanks for the suggestion, mungulz, but i suppose we don't have the same problem. i went through all my internal AND external data and saw nothing out of the ordinary
on that note, introducing another twist in this ridiculous predicament, NO app (and with the exception of root explorer, NO app) can see my songs (external sd). if i use root explorer to force an app to use it, the app force closes
and just a thought, but i keep fixating on the .PIT file. your thoughts?
Have you done a full wipe including user data? Might be something left over that us causing issues, take a titanium backup first though
Sent from my GT-I9100 using xda premium
if you mean the CWM one, then yes, plenty of times. basically, each time i flashed something on the phone in this period, i factory reset. if i do it now, that will temporarily solve the problem and i'm pretty sure of it. one reboot later, i'll be back in hot water
i'm aware, of course, that there are other ways of factory resetting...
1) Flash Stock KI3, with pit file and re-partition
2) Back up everything including the int. SD to my PC.
3) press *2767*3855# it will completely wipe your device.
4) Once phone reboots, place custom rom and pictures + titanium backup onto the int. SD
5) Flash a custom Kernel
6) Reboot recovery, wipe data, wipe system, Flash Rom.
7) Reboot and restore the DATA only
or without pit file and uncheck re-partition
i had to go for tuition, so i couldn't do all the things gasmias said; just factory reset with *2767*3855# and then restored the apps ONLY with TB. and...my phone is back!
huge thanks to all of you for trying to help (lol, too many thanks buttons to press) . i guess it was just corrupt left overs. but dammit, now i'm scared of putting VRTweaks back in . eh, i'll take a nandroid back up
in light of these events, anything i should keep in mind for my future flashing endeavors?
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 ...
Hi,
I tried 10-15 diffrent custom roms and maybe 5 kernels. On everyone, except Sensation, SGS2 reboots very often. Sometimes is 2 times in hour, on CheckROM reboots after 1-2min after SGS2 is on. I tried diffrent base and still the same issue. For now I back to stock KI4 and for three days it hasn't restart even once. Anyone got idea how to fix it? SGS2 is brand new, I can send it for warranty repair, but what I tell him? It restarts if I install custom rom? I don't think so
Of course I did full wipes before install new one, install two-three times same rom and even don't install any apps. Still rebooting, except stock and sensation I don't use external SD card.
So I must stick with stock rom or sensation? No way, I love to flash new roms
Cheers
You're missing some key info like did you try to wipe the phone/data/cache did you undervolt/underclock... and the list goes on.
Ok, here is the list what have I done, from the begining:
- stock rom was KE7, I instal proper CFroot on it
- next I install Sensation via CWM
It was good, but little slow, quite laggy, slower then my SGS (i9000)
- install CheckROM v4 via CWM
Great speed, but reboots
- install speedmod from kitchen, nothing improves, keeps rebooting
- from now I can't remember, I check various roms and kernels, nothing improves
- back to sensation, great speed (same version than on the begining, but a lot faster), no reboots
- install stock KI3, change PC to XEO, upgrade via KIES to KI4 and everything is ok
- I don't change clock speed or anything else, just change roms and kernels
Please state more of your phone info... current android version etc... country of origin that kind of normal stuff - about phone etc
Edit - before you do the below - make sure you have the right version phone etc...
Maybe post up your phone details to be sure...
As a test please dl the rom in my sig - top one - illusion
Check md5 sum as always you should
Reboot to CWM
Wipe data
Wipe cache
Wipe dalvik
Install zip from memory
Reboot
- set up the basics but not wifi etc ( I say this so that apps don't auto download which slows phone down loads at first ) ... leave 10 - 15 mins just sat on the side not touching a thing...
Reboot again and finish setting up your phone... Tell me if you have lag etc...
If you do then start completely from scratch - flash your original firmware ... return completely stock - and start fresh
SGS2 was brand new, bought about 10 days ago in polish GSM operator PlusGSM. Stock rom was 2.3.4 (?) XXKE7 branded by Plus. Now it is 2.3.5 XXKI4, without root and CWM, just clean stock XXKI4.
I'll try with Illusion and give you a feedback how it goes.
goofy3 said:
SGS2 was brand new, bought about 10 days ago in polish GSM operator PlusGSM. Stock rom was 2.3.4 (?) XXKE7 branded by Plus. Now it is 2.3.5 XXKI4, without root and CWM, just clean stock XXKI4.
I'll try with Illusion and give you a feedback how it goes.
Click to expand...
Click to collapse
Not the most popular but I know its stable ... So model number is - GT - I9100 (no letters on the end?????)
Just GT-I9100, no letter on the end, black version.
Under battery: SSN: -I9100GSMH
After some time with Illusion XT:
- it superb fast
- no lag
- no restart
- one freeze (during installing apps via appbrain) and only removing battery helps
goofy3 said:
After some time:
- it superb fast
- no lag
- no restart
- one freeze (during installing apps via appbrain) and only removing battery helps
Click to expand...
Click to collapse
In your dialer put *#1234# and post exactly what there is
PDA: I9100XWLA4
PHONE: I9100XXLPB
CSC: I9100XXKJ3
Build Info: Tue Jan 17 15:09:29 CET 2012
goofy3 said:
PDA: I9100XWLA4
PHONE: I9100XXLPB
CSC: I9100XXKJ3
Build Info: Tue Jan 17 15:09:29 CET 2012
Click to expand...
Click to collapse
Ok, first dl Checkrom V6 ... its on LA4 base with cf-root wich works very well with me. Push the file to your sd card and flash with cwm.
http://download.checkrom.com/roms/a...vo_HD_V6.zip?iframe=true&width=950&height=420
Do that first ...
EDIT: dont forget clear cache/dalvik
ITRC said:
Ok, first dl Checkrom V6 ... its on LA4 base with cf-root wich works very well with me. Push the file to your sd card and flash with cwm.
http://download.checkrom.com/roms/a...vo_HD_V6.zip?iframe=true&width=950&height=420
Do that first ...
EDIT: dont forget clear cache/dalvik
Click to expand...
Click to collapse
Originally Posted by goofy3
After some time:
- it superb fast
- no lag
- no restart
- one freeze (during installing apps via appbrain) and only removing battery helps
Why???? Sounds like backup coprruption to me - all was fine until then
I tried CheckROM v6 at day when it was released and I get reboots. So far I'm happy with Illusion, so I stick with it for few days and see how it works.
Maybe something went wrong when I install CFroot first time, and after flashing stock again it back to normal. I hope so...
@BigMrB, it wasn't backup, only fresh install from market, but using appbrain fast install. Maybe too many downloads in background casue freeze.
BigMrB said:
Originally Posted by goofy3
After some time:
- it superb fast
- no lag
- no restart
- one freeze (during installing apps via appbrain) and only removing battery helps
Why???? Sounds like backup coprruption to me - all was fine until then
Click to expand...
Click to collapse
Is your device running fine already then??
goofy3 said:
I tried CheckROM v6 at day when it was released and I get reboots. So far I'm happy with Illusion, so I stick with it for few days and see how it works.
Maybe something went wrong when I install CFroot first time, and after flashing stock again it back to normal. I hope so...
Click to expand...
Click to collapse
I've never had a single reboot / fc for 2 months using illusion
I edited previos post, maybe too many download in background cause freeze. And after that, everything runs smooth without any problems
BigMrB said:
I've never had a single reboot / fc for 2 months using illusion
Click to expand...
Click to collapse
Ah ok then... But If you go to another rom, read the instructions very good. Sometimes you have to wipe cache/dalvik etc ...
goofy3 said:
I edited previos post, maybe too many download in background cause freeze. And after that, everything runs smooth without any problems
Click to expand...
Click to collapse
Good Luck ...
Just a quick note. You didn't state if you wiped the phone before flashing a new rom. Do that and then see if there are any problems. Most rom problems IMHO are usually a result of flashing a new rom and not wiping first.
bpivk said:
Just a quick note. You didn't state if you wiped the phone before flashing a new rom. Do that and then see if there are any problems. Most rom problems IMHO are usually a result of flashing a new rom and not wiping first.
Click to expand...
Click to collapse
Yes, I do wipes (data, cache, dalvik) before every flash, sometimes I tried even after, or after first boot, no luck. I've got some experience after few years with flashable devices and year and a half with I9000 Problems comes with I9100...
Ok, after one day with Illusion XT:
- normal use (using for 2-5min continuously, make call, send text, fast check www or email) - everything is ok
- extended use (using for 15-30min continuously, browsing web, tapatalk, wrote emails etc) - one freeze
- heavy use (using 30min and more continuously, web, some YT movies, playing Dead Zone) - freezes, restarts, freeze and restart, generaly everything was falling apart. I have no FC's, but some apps starts and close after few seconds. I must left phone for some time and then everything back to normal. One more thing. Before playing Dead Zone, battery was 60%. I played maybe 5min, then freeze, restart and battery was 25%. What the hell??!!
So, my only thought is overheating CPU/memory. I read that S2 getting hot is normal, but maybe my CPU/memory is less tolerant. It's my only idea, and I say this again, I don't ever change frequency of CPU or memory. Governor is set by default to lag free. Of course I can lower frequency or change governer to slower, but it's pointless.
I'm so much closer to send it to warranty with note that is restarting at heavy use. My only hope is that they don't just upgrade FV like they used to do.
I will do it on next week, so maybe during the weekend someone will post an idea what else could it be. But please, don't tell me to flash other rom or kernel, I check douzens of them, it's something else.
*READ BELOW FOR A GUIDE TO FIX*
I've had my note for over a year now and i have had it rooted pretty much the entire time. Never any problems with it up until recently it started doing this thing where it would keep restarting. It would boot up and less than a minute later just restart. Off and on for a few days it was doing this. I was still running 2.3.6 at that point. So i decided to push 4.0.4 via odin since kies didnt support the firmware. Everything was working fine for a few hours then all of the sudden "the ring of death" showing me no service. Went through the phone and noticed it was saying there is no sim inserted. Tested sim on another phone. Works fine. Since then ive figured out via kies i can recovery and update firmware. Tried that. No Bueno. Now im to the point where im on 4.0.4 with no service. I've scoured through forums trying all kinds of different things, pushing different roms and modems via odin and cwm. Still no bueno.
Baseband version
Unknown
Kernel Version
3.0.8
Build Number
IMM76D.UCLF6
If anyone can give me ideas im willing to try them out.
Thanks.
I got it working so heres a direction for anyone else who has this issue!
Replaced Sim&SD card reader-No fix
After flashing all kinds of roms & modems still same issue saying no sim inserted.
Do a hard reset through your settings.
Flash cwm and put the radio from this link on your sd card. Use cwm to flash the radio.
Flash rom http://forum.xda-developers.com/showthread.php?t=2261598 via odin.
The first try i got an error during flash and got stuck on the software download error screen.
Reflashed the JB rom.
After its flashed flash clockwork recovery.
Enter cwm and do a factory reset. Clear cache. Clear dalvik cache. Reboot system.
If you get service, turn off phone. enter cwm and do a backup.
Reboot system.
It should be working.
If not restart and make sure to do a factory reset through your settings in the phone before reflashing rom.
Got the Phone up and running for about 30 mins.
After battery removed it reverted back to no sim card inserted.
Kept reflashing rom until it worked again.
Flashed cwm.(ClockworK recovery mod)
Deleted cache, dalvik cache
Backed up via cwm
If it reverts back to no sim after that restore using the cwm backup.-it worked for me
Now for the tricky part, my phone was getting crappy service...
So heres what i did to fix it.
Settings-more settings-mobile networks-access point names-click on the apn.
Name-
ATT Phone
APN-
Phone
Proxy-
Not set
Port
Not set
User Name-
Not set
Password-
Not set
Server-
Not set
MMSC-
http://mmsc.mobile.att.net
MMS Proxy-
proxy.mobile.att.net
MMS Port-
80
MCC-
310
MNC-
410
Authentication type-
None
APN type-
default,admin,fota,mms,supl,hipri,internet
APN protocol-
IPv4
Enable/disable APN-
(check mark)
Bearer-
Unspecified
Hope this helps anyone else having this issue.
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
440bro said:
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
Click to expand...
Click to collapse
I Started from scratch via "kies emergency recovery".
No luck.
dweeezy said:
I Started from scratch via "kies emergency recovery".
No luck.
Click to expand...
Click to collapse
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Stuck power button. Your pants are too tight.
Theoriginalgiga said:
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Click to expand...
Click to collapse
i ordered a new sim port to see if that works. what is gb?
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
dweeezy said:
i ordered a new sim port to see if that works. what is gb?
Click to expand...
Click to collapse
GB stands for Gingerbread which was the first version of the OS that came with the phone. I believe the number was 2.3.6 (you can take a look in the about section in the settings and it'll tell you what you're currently running). ICS is Ice Cream Sandwhich which for our phone was 4.0.4 i believe. Jelly bean just came out today which you can use Kies to upgrade to and that I believe is 4.1.2. The numbers don't really mean a think, just the classification of what the OS is so if your phone reads something else (say 2.3.4) assume your phone is right and I'm wrong. I can't remember OS versions to save my life haha.
But you can use Kies to do an emergency recovery and I THINK it'll install Gingerbread. that's where I'd start, then test it, and then move to ICS and test, and then move to JB and test. I know long tedious process, but sometimes it's necessary. Imagine how fun I am to talk to on the phone while troubleshooting a computer :laugh:
redman9 said:
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
Click to expand...
Click to collapse
what I use to migrate, and I between roms at least once a week with a full wipe because I rely on my phone being stable.
SMS and call logs: SMS Backup + (saves your call logs and sms to your gmail account. Makes a label for it and everything, pretty sweet. You can also restore from it. it takes about an hour for me to restore at 7000+ text messages).
pictures/media: stored on SD card
apps: if rooted and rommed I use titanium backup and run 2 sets. those which I want to keep my data like sms backup + to make restore easier and those I don't care about the data like google voice. If you're stock, just remember to check the little box in the beginning saying backup this phone to google (or something like that) and the next time you have to restore tick the box that says restore from google (or something like that) and it'll reinstall your apps. Mind you not the info, but it'll give you a head start.
As with your issue with installing roms. If you're using CWM i highly recommend switching to TWRP, not saying it's better in fact I like CWM better, but TWRP is the best for our roms and phone. If you have no clue what I mean by CWM or TWRP, read the all info sticky about how to rom thy phone.
I hope that helps.
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
redman9 said:
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
Click to expand...
Click to collapse
No problem always happy to help. since you're used to this sorta thing you don't need to use odin again and reroot. What you can do is either install TWRP through CWM using this file here:
http://goo.im/devs/OpenRecovery/sgh-i717/openrecovery-twrp-2.5.0.0-quincyatt.zip
Or you can install Goo manager, click settings and select Install OpenRecoveryScript (though that's only 2.4.4.0 the link above is 2.5.0.0)
That should change you over to TWRP. and like always do a nandroid backup and then flash to your heart's content!
fixed!
dweeezy said:
fixed!
Click to expand...
Click to collapse
How ?
galinha said:
How ?
Click to expand...
Click to collapse
i have the same issue.....i kn0w its n0t an hardware issue....my ph0ne is fairly new never dr0pped and this started happening 3 days after i p0rted black star jb alpha
I have this same issues ive tried flashing everything ive tried a new sim and replaced the card reader.
What works consistently for me if to flash the latest modem everytime i have to reboot or boot the note. Its my daughters phone now and she drains the battery regularly if it boots after charging or it needs to be rebooted for whatever reason it will come up with the no sim card error. If i flash the modem thru recovery it will work for that boot but only as long as I dont reboot or shut the phone off, then i will have to flash the modem again.
Not fixed
All. This is not fixed. I am having the same issue and if you follow the guide, it works for a day maybe regardless of what rom is loaded or what modems. Has anyone found a real solution to this yet??
i717 running stock GB or ICS or JB roms...
Thanks!
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Kraize said:
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Click to expand...
Click to collapse
I'm having the same problem. There seems to be no set way to get it back to working. Basically any reboot of the phone produces a no sim card error. I have tried flashing the modem through recovery as it was mentioned that will fix the problem. That did not work for me. What does work, sometimes, is one of the following:
1. Full wipe and reinstall
2. Restore backup from Recovery
3. Fix permissions
I just keep doing one of the above listed and eventually it works. However if the phone reboots then it's back to the carousel of trying these options to get it back to working.
I'm running Padawan JB V2
I honestly have no idea what's causing it. I haven't tried to fix permissions before to fix this issue, but if I go into recovery and install the modem again and reboot, it works fine for a while (and by a while, I mean like a few hours at max).
Just started having this issue, myself...after flashing Tmo_SGH-T989_VKL1_radio_ATTNOTE.zip modem on my phone...restoring from a prior backup...
Restoring a backup will not change your modem.