Related
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 ...
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Sent from my GT-I9300 using XDA Premium HD app
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
solarisrulez said:
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Click to expand...
Click to collapse
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Guys, Thank you all, trying to reply to everyone:
Enea307 said:
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Click to expand...
Click to collapse
Thanks, maybe I'll give that one a go as first try.
converse5 said:
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
Click to expand...
Click to collapse
No, I'm pretty sure that's not the case. Checked my router admin configuration tried to enter my wi-fi pass about 30 times before giving up.:laugh:
chrismast said:
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
Click to expand...
Click to collapse
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
lefttobleed said:
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Click to expand...
Click to collapse
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
solarisrulez said:
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
Click to expand...
Click to collapse
(1) The best would be to read the mega wipe thread. I use it all the time, it will delete ANYTHING excep the external SD card (also not EFS etc, hence dont worry). Therefore you need a flashable rom on the external sd or via Odin later on. But basically your phone won't start after a mega wipe, just download & recovery will work.
Your wipes are correct I think, whereas /system is missing wich is needed, at least for SlimBean (4.3).
(2) The best would be to read the guides & kernel thread's how-to's first. It is basically the same as flashing a rom, yes.
solarisrulez said:
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
Click to expand...
Click to collapse
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Misleading title .
#There have been a number of identical posts and some have fixed by copying older WiFi files over . But you need to search and read and no i don't know where they are . .
Its not a custom rom problem but a non Samsung custom rom problem on 4.3 .
jje
lefttobleed said:
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Click to expand...
Click to collapse
Yes, reading the guides, so first of all decided to backup my EFS (coz that sounds reassuring before doing more ROM flashes) with EFS Professional from this thread: http://forum.xda-developers.com/showthread.php?t=1308546
Installed BusyBox on my phone, and I'm stuck because of a missing applet: http://cl.ly/image/1a1J1A0I3V0H.
I think I'm going deeper than what I can handle
BTW, Enea307, tried CM 10.2 (4.3) this morming, and same wi-fi problem. So it's most likely not a custom rom issue, as most of you suggested.
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
JJEgan said:
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
Click to expand...
Click to collapse
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
Done everything according to http://forum.xda-developers.com/showthread.php?t=1671969
And the firmware is also the one for my phone, and the *.zip that contained the tar (md5) is not damaged http://cl.ly/image/322h3634211J
Any ideas? thx!
solarisrulez said:
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
JJEgan said:
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
Not installed KIES yet, as I read that that's a big brother or something to Odin, and that his little brother is much better at flashing. Should I give KIES a go? Anyways, trying to redownload the firmware.
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
JJEgan said:
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
Click to expand...
Click to collapse
I had installed Samsung Drivers beforehand, before even rooting / doing anything. Did not had KIES until now.
Still cannot flash to stock firmware with Odin.
BTW in the guide: http://forum.xda-developers.com/showthread.php?t=1671969 i see that it should be blue, but mine is yellow when I connect my phone to Odin: http://img600.imageshack.us/img600/9231/odin4c.jpg and mine: http://cl.ly/image/473N1E0Q3G2X
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
IC3CR34M said:
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
Click to expand...
Click to collapse
Thing is, that I am rooted, done with Odin, by following this guide: http://www.androidrooting.com/how-to-root-samsung-galaxy-s3-gt-i9300-or-gt-i9300t-cwm-recovery/
So I have CWM, and with I tried Android 4.3 via SuperNexus, Android 4.3 via ParanoidAndroid 3.97 ROM, then, lastly CM 10.2 (4.3). With none of them did I managed to get the Wifi going.
Here is my current "About device": https://www.dropbox.com/sc/8hp04dn5o5flytd/LpoJCgZ7sK
Is this stock samsung firmware? Coz I can't tell. It seems stock, but maybe it changed with the rooting procedure.
So I repeat, only with this setup/build does the wifi work. With no other custom rom does...
I did backup and recovery to my current working wifi rom. That's how I recovered after trying these custom roms mentioned before.
Guys, help me pls, with at least flashing to the stock samsung rom with Odin or Kies (Odin failed, scroll up see my recent posts with screenshots)
Note that on my last try, Odin just froze yet again: http://cl.ly/image/0o0o0k2L3J3m
If not with Odin, then how do I restore it to stock samsung rom with KIES?
thx!
You dont do it with kies. Kies is such bull**** software. Dont use it at all. You wanna backup, use TI(titanium backup) or nandroid backup. Take a system backup from CWM. As you said in your post, u want to go back to stock, dl the stock rom, do the same procedure u did to root your phone via odin (pda, etc etc), just this time instead of the root zip file, just put the stock rom zip file.
It should take some time, and aftet its done, your phone will be as good as new. To restore the backup via TI, dont select system apps. Only the apps which are in green font or downloaded apps. Other wise u will have force closes.
Also, when u flash the stock rom via odin from your pc, you will not have root. Just a note.
You can simply remove bloatware like live wallpapers, samsung "never gonna use" features like Svoice via TI by just uninstalling them, but note, if fiddling with system apps, them make sure u take a backup.
I have written it all in simple language so that you understand every essential part and have fun with your rooted phone.
Happy to help
As always last resort restore original firmware with Kies and probably a better method than some others posted.
SEE The how to restore your original firmware using Kies post .
Sent from my GT-N8010 using XDA Premium 4 mobile app
Hi, I'm having a really difficult time with my S3. I've rooted and flashed it with Supernexus 3 (4.3) however it has been constantly locking up and freezing randomly. Approximately 15 times a day. I have now reset/data wipe the phone and reflashed the ROM but same issues. I have also tried CM10 Official nightly build and it still locks up. I have tried it with and without restoring user apps + data. What could the problem be anyone? Any help would be appreciated.
The problem could be your custom set up, factory reset and flash a stock 4.1.2 rom to test.
If it still freezes on stock then you probably have bad memory blocks, go read the 'unusual freezing' thread in the general forum.
boomboomer said:
The problem could be your custom set up, factory reset and flash a stock 4.1.2 rom to test.
If it still freezes on stock then you probably have bad memory blocks, go read the 'unusual freezing' thread in the general forum.
Click to expand...
Click to collapse
Thanks for reply. Will check that tonight. How do I know what's thet stock ROM for my handset? I have a sim free s3 and based in UK.
If it doesn't freeze on stock then what would you suggest?
See sammobile.com for stock roms .
No freeze on stock bad rom faulty flash a bad file wrong instructions etc etc .
jje
boomboomer said:
The problem could be your custom set up, factory reset and flash a stock 4.1.2 rom to test.
If it still freezes on stock then you probably have bad memory blocks, go read the 'unusual freezing' thread in the general forum.
Click to expand...
Click to collapse
JJEgan said:
See sammobile.com for stock roms .
No freeze on stock bad rom faulty flash a bad file wrong instructions etc etc .
jje
Click to expand...
Click to collapse
So i've been on stock rom for the whole day whilst also rooting again and haven't had any freezes whatsoever. Even when restoring apps using Titanium Backup there were no freezes. Under custom setup there were multiple freezes alone whilst restoring apps. I doubt I have followed instructions incorrectly (don't mean to sound like a [email protected] ) but I have flashed ROMs multiple times before with no issues, and hey, even managed to flash back to custom ROM successfully. I just don't get how I can have the same locking/freezing issues on 2 separate ROMs (CM10, Supernexus) but not have it on stock ROM.
I had a look at the unusual freezing thread and I thought it may have applied to me as my phone has been fixed to repair the 'Sudden death' fault but after flashing stock rom, I have had no freezes.
Any ideas? I have put back my Nova Launcher configuration however it just feels clunky with stock rom. And oh, it's still 4.1.2.
I want 4.3 Supernexus
Hello every 1. before i doing something with my mobile phone i thought might as well get a help. i have got Samsung Galaxy S2 GT-i9100 Jelly bean 4.1.2 build number XWLSW, My phone is very very laggy i dont know why, i have got alot of space in my mobile and i dont have many apps in my mobile, Its very laggy sometime it just get stuck and i have restart the phone again, I was thinking of rooting the phone, I have rooted the phone after 5 hours of looking around Now i just want to know how can i flash my mobile with a good stable rom so i can run my mobile smooth, Does all roms are compatible to my mobile phone i just downloaded CyanogenMod 10 before doing anything i wanted to wather this is compatible with my mobile or not and what else do i have to do.
Hi,
if you download the right build from CyanogenMod 10 there is no problem, watch out for "I9100" in the buildname.
But if you want to stay on stock it would maybe help if you do an factory reset in the recovery
Andi
http://www.sammobile.com/ download the rom of your country and flash it... these are stock roms (no rooted) if you want stability... just back up and wipe everything... factory reset..wipe cache after flash the rom... and format of your internal sd...
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?