The title pretty much says it all. This has been going on for a while now, and it's starting to annoy me. Does anybody have a fix for this? I couldn't seem to get any of the fixes from other Galaxy S devices to work.
did you revert to stock from cm7?
SpaceToast7 said:
The title pretty much says it all. This has been going on for a while now, and it's starting to annoy me. Does anybody have a fix for this? I couldn't seem to get any of the fixes from other Galaxy S devices to work.
Click to expand...
Click to collapse
The only time I have seen this happen is when returning to stock from either the CM7 betas or any of the ROMs built off of it, and the reason for it is you lost your EFS data and unless you have a backup of that (CWM backups DO NOT have this backed up).
If you do indeed have an EFS backup then you can use Zaclimon's recovery thread and just add the EFS to that, that is the proper fix.
If you where a total newb like I was and completely lost it because you thought a CWM backup was enough, the only "temporary" fix is to flash Klin's IcyFusion, Han's Etheral or Dream Ultra then reboot into CWM recovery and "wipe data / factory reset" then reboot player, this will restore the boot menu and lockscreen for aslong as you run any of those ROM's but if you go back to stock it will vanish again.
Well, I somehow lost it when I wiped data on klin's klassic. A restore of data fixed it, and I haven't wiped my data since or gone back to stock so idk if it is still there.
Sent using Tapatalk
Thanks. I guess i will be using one of those roms you mentioned.
UPDATE: Ethereal did not fix EFS. As a matter of fact, it broke my home button.
SpaceToast7 said:
Thanks. I guess i will be using one of those roms you mentioned.
UPDATE: Ethereal did not fix EFS. As a matter of fact, it broke my home button.
Click to expand...
Click to collapse
Using Zaclimon's recovery method to go back to stock is the only way i've been able to fix the home button when Ethereal broke mine (this seams to be another side effect of losing the efs). restore to factory with zac's method thru heimdall (using a different usb port other then the one used for Odin) then Odin flash to Icy Fusion and Terrasilent kernel and follow previous instructions.
I did go back to stock rooted, and i think i will be staying there for the forseeable future because it seems that there arent any mature kernels or ROMs for this device - too unstable.
At any rate, am i correct in assuming that my EFS issues are related to (the abomination that is) TouchWiz, and that AOSP builds of Android do not have this issue? Ive never heard of this outside of Samsung devices.
Sent from my YP-G1 using xda app-developers app
SpaceToast7 said:
I did go back to stock rooted, and i think i will be staying there for the forseeable future because it seems that there arent any mature kernels or ROMs for this device - too unstable.
At any rate, am i correct in assuming that my EFS issues are related to (the abomination that is) TouchWiz, and that AOSP builds of Android do not have this issue? Ive never heard of this outside of Samsung devices.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I don't think so, what happened to me was I flashed one of the CM7 beta's and since they convert every partition from rfs to mtd it messed with my efs partition and so since I didn't have a backup of the EFS it was lost (CWM backups DO NOT backup the efs), from what I have gathered it holds your serial number and stuff like that which is why the deviceID hack implemented in Icy Fusion is able to "fill in the blanks" and that is what causes it to come back while on that ROM, I don't see how it can have anything to do with touchwiz, I use LauncherPro myself.
Icy Fusion and Dream Ultra are stable ROM's I haven't had any problems with them (other then Dream Ultra coming up in Russian after doing a wipe data/factory reset, but thats easy enough to fix) and the Terrasilent kernel is totally functional as long as you don't reboot into recovery on a ROM where you've converted all partitions to ext4, just load up a program like Tegrak or my choice of No Fills CPU tuner and change the governor to smartass V2. I couldn't conceive running stock at this point.
Related
I installed Cyanogenmod 7 a week ago, and everything was pretty much working fine.
Randomly today, all 4 of the soft buttons stopped working in the middle of me using my phone. I believe I was checking scores on an NFL app. Regardless, reapplying the CM7 zip didn't fix it. I tried factory reset, wipe cache, wipe dalvik cache. Nothing.
Decided to try to reroot. Reapplied ED05, which is what I did before I installed CM7. Got back to essentially factory... soft buttons still don't work. Reinstalled CM7... took, but soft buttons won't work.
I thought I read somewhere that this is an issue with gapps, but I can't seem to find that page or people discussing it again. Installing gapps again didn't work.
I'm willing to get my phone back to it's most basic level, and even erase the SD card if I need to, but not sure how to clear my phone moreso than my reverting back to ED05.
Thanks for your input guys.
Also, I had reinstalled my apps using Titanium, but not the app data. Again, everything was just fine for a week.
Also, having done a bunch of flashing and what not, I dont' know what happened, but now when I long press the power button, the menu comes up. When I try to use volume up/down to navigate to power off, all I get is volume going up and down
So, i know this thread is sort of dead, but this happened to my fascinate a while back with a version of CM7 mtd (55 maybe?)... I'm fairly convinced that the sensors for the buttons (and the lights for that matter) are completely shot, but I can't really test that. I have flashed back to stock, re-rooted it,and done everything I can think of to fix it.
You probably messed the phone up for good... my advice (if you haven't already done it): get a new phone.
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Will try this out
JJ5150 said:
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Click to expand...
Click to collapse
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Charcaroth said:
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1488976
If you are already on ICS just wipe cache and dalvik cache and flash. If not just flash up to ICS and flash kernel with ROM (same cwm session). You may want to do some reading in that thread first to make sure you get right version for your ROM.
Sent from my SCH-I500 using xda premium
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?
This phone was an insurance replacement from ATT, so alway a bit wary of these refurbished phones.
So for the longest time it has always been a bit glitchy, hanging, and unstable. I assumed it was a software problem, and something i had done wrong when flashing...but now I am wondering if maybe my phone is a lemon. Lately it has been rebooting randomly on its own,
I wanted to try flashing back to stock, just to start from scratch, and I did with Da G's stock rom . Then i just rooted it with Da G's root, and put on CWR. Then I flashed King Kang Rom. It's been still real buggy. Maybe I need to to stock ICS or JB then flash a ROM? OR maybe it's just this phone....either way not real happy with the stability i've been dealing with.
If youve tried multiple roms and stock roms and its still buggy then its probably the phone, I have got so many replacement phones that were duds
Are you doing a wipe between all those roms or just flashing one over the other? That could be a major problem that is easily fixed.
Yes, i do full wipes/factory reset in CWM every time.
I know i have seen some guys say you must flash like 3 times, so maybe i'm not flashing it enough times or something..? i also saw someone say don't touch your phone for 15 minutes after flashing. i have no idea if these tricks actually work or what. doesn't seem to be a definitive rule book on how to flash the right way
How are you restoring your apps? TB or letting Play reinstall them?
using TB. I usually do a just apps reinstall, then data
Was the TB backup from a different version of android, i.e. GB, ICS then installed on JB?
yes, i did create it on an ICS rom. you think that could be causing me problems?
Good possibility. I had the same issue. Moved from CM9 to CM10 and restored through TB. Lots of FC and reboots. Wiped and let Play reinstall everything, now its smooth.
great thought and worth a shot if that's what could be causing a problem. so did you lose all your data then with all apps? msgs, etc? sucks to start from complete scratch. i'll even miss call log
Lost data, but was able to d/l everything else. Messages and call logs were gone. It is worth it to have a working phone with out glitches. Let me know if it works.
Well a good test is to install a known solid ics problem free ROM like Padawan or Black ice? (exact name escapes me). If it works for u then over clock it to 1836 with setcpu and u will have a ROM VERY close to the JB rom smoothness but actually works.
If u still have problems then u may very well have a flaky phone.
(Oh yeah don't get to worried about stuff like wipe 3 times etc...old wifes tales. I haven't done that for over a year on 3 android phones. ). Also it is Safe to restore apps AND data with titaniumb (just not system data).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
+1 on the old wives tale. Seems more like a placebo effect. I only wipe once, and I've flashed roms on tons of phones.
Sent from my Galaxy Nexus using xda premium
tried installing padawan...so far so good, have not overclocked yet....will report back
Some roms will format your system partition prior to flashing the rom while others do not.
Beyond the wipe of data, cache, dalvik and such, it is wise to go into " mounts and storage" and format the system partition while in CWM recovery.
This ensures that nothing remains on the device before the new rom image is pushed to the system partition.
I agree that wiping 3 times is a bit over the top, but wiping the entire image base before flashing a new one is almost always mandatory.....g
For future reference, you can back up call and sms logs and restore them without causing lags or fc. The logs are simple .xml files.
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Phitherek_ said:
Hello,
Every once in a while my Samsung Galaxy SII I9100 with Android 4.1.2 hangs up, and after that it goes in the bootloop on power on. And I know that hard reset is a solution to this problem. But it happened to me lately like 4 times and I really HATE losing my data from apps and settings like this. Is there any way to fix it WITHOUT the need to hard reset? I tried the "soft reset" but it didn' t solve the problem. Every time it is like this - the phone hangs up (usually overnight), I turn it off and then on and suddenly it is in a bootloop. I can access the Recovery and Download modes.
Click to expand...
Click to collapse
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
andrewwright said:
Have you tried to change kernel see if that helps? Philz is stock solid kernel no probs my end.
Click to expand...
Click to collapse
Actually I never tried to change the kernel, I am now using Samsung' s original 4.1.2 firmware. Thank you for suggestion.
MistahBungle said:
Had a similar problem with a Dorimanx build late last yr (forget which build exactly), every couple of weeks the same issue as you're having.
My solution ? Make regular nandroid backups (at the very least weekly, more often if you're updating apps/making changes to your setup a lot or if the problem is happening really often), and restore same whenever you have the bootloop problem.
Worked for me until the problem went away with a different build.
Edit - Or you can do what Andrew suggested & try another kernel/different build of the same kernel (If you're going to stick with the same kernel, tell the dev/pull a logcat or whatever & give that to them).
Click to expand...
Click to collapse
Thank you for suggestion, however my device is not rooted (yet?), so I cannot use nandroid.
Flash with philz kernel and it will be I love team work Mb :thumbup:
Running pure stock, your options are basically zero short of doing a factory reset, which may not solve the issue. You could do a clean install of stock via Odin, but if you're going to go down that path you may as well go the whole hog & root the phone (you don't necessarily have to run a custom kernel/rom if you don't want to; plenty of people run rooted stock) and receive the benefits of same (I.E the ability to make nandroid backups - much better than any other option Samsung has ever come up with).
Thank you for redirecting me to PhilZ kernel. However, I do not know which version I have to download for the Polish firmware (XXMS1), could you clarify?
Also, I have found a Siyah kernel in my search, flashed beta4 but it does not work for me, should I try with beta5? And is it a good kernel?
Siyah v6.0b5 will work and philz lsw will work siyah is very good so is philz
I had exactly the same problem this morning.My phone originally had omega v23 (with philz) installed, but it kept running hot all the time, so I flashed stock 4.1.2 xwlsw with mobile odin and everroot. My question now is should I unroot my f/w before flashing philz kernel?
No just flash it will do as its told :thumbup:
andrewwright said:
No just flash it will do as its told :thumbup:
Click to expand...
Click to collapse
thanks. In the meantime I've doing some reading and somewhere in the depth of the philz kernel thread was a post buried, where some recommended to flash the tar file via mop. That's what I've done. It seems to have worked.
But it's running hot again. I had that before with the philz kernel, but that belongs in another thread
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
andrewwright said:
Ok but give it 20 mins atleast to settle down. The only kernel other than apollo that keeps my phone cool :thumbup:
Click to expand...
Click to collapse
Dumb question, but I find I need to flash apolo, can I just go ahead and flash it in recovery over philz or is there something I need to look out for. Also I've read about scripts for cleaning up busybox and previous kernels? this is all very confusing
Use gs2 kernel wipe script flash script first then flash dif kernel.
this
Ok, I probably accidentaly found a cause of this problem. I had Facebook information on my lock screen and when I tried to refresh it my phone went on bootloop. So probably it is the issue with the information module of the lock screen (or maybe it was just a coincidence, if so, I will let you know). I think everyone with XWLSE firmware should consider disabling this feature. Btw. really thank you guys for PhilZ recovery + root kernel and Online Nandroid Backup suggestions, they are great .
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?