I am relatively new to android and had a question. I have my phone rooted and installed the BAMF Remix ROM. I have also changed the radio to the one recommended in the original BAMF Remix thread. I have been having problems with the phone doing a factory reset upon reboot. The phone is not rebooting by itself. But occasionally after I shut the phone off, when I power it back on, it has done a factory reset and I have to set the phone up again. I have had this occur with the BAMF remix 1.5, 1.6, and 1.7. My phone's baseband version is 1.16.00.0402w_1.
Can anyone tell me if this is the result of the ROM? Could it be the radio or maybe an app? Any help or advice would be appreciated. The BAMF Remix has been working great for me in terms of battery life, its just getting to be a pain to set up the phone again every week.
Thanks in advance.
Hmm.. I haven't tried the BAMF ROMs yet,but I've never had a phone reset itself like that.. Odd.
I'd suggest trying a different ROM for a bit and see if that stops it. If not, you may have an issue with the phone's memory or maybe even the SD card?
In the meantime, I'd grab Titanium Backup. The pro (Paid) version would be best, but if you don't want to pay for it just use the free version and back up all your apps and settings. Then if it happens again, just restore those. OR set up the phone the way you want and do a Nandroid backup in clockwork recovery. That way you can boot back into recovery next time it happens and restore a working backup with everything already set up.
Hope you figure it out soon.
i personally would clear everything three times or more;cache..data, dalvik, and battery stats. and use recovery not Rom manager then check the MD5 sums on the radio and rom to insure they are not corrupted in anyway. and i would strongly suggest using titanium back up;it will save your apps, and the data for apps, and system settings, its really a great tool
Related
Hello everyone,
I have been reading these threads for a while, getting prepared to root my Thunderbolt. I rooted about a week ago with Revolutionary and had no problems whatsoever. A couple days ago I flashed my first ROM (Gingeritis) using the instructions on this forum, and everything worked great, except that I accidentally restored some system data with Titanium Backup, which I read can cause FCs, etc.
Therefore, I restored the stock ROM by booting into recovery and following those steps. Again, everything went well.
This morning, I wanted to try out a different ROM, so I followed the same steps with das BAMF 1.10, and I flashed the ROM successfully with no problems. However, after restoring my contacts (one of the green pieces of system data that I thought were ok to restore) with Titanium Backup, the popup "Sorry!" repeatedly came up saying that the application.com.android was not responding and needed to be force closed. It came up again so fast after clicking "close" that I couldn't even reset. Finally, I pushed the power button at the exact right time to be able to see the menu of options, and I clicked restart (not in recovery).
Now, the phone is running through the das BAMF and HTC startup screens repeatedly. The battery is pretty low. What do I do???
Thank you so much! I really really want to resolve this and avoid bricking my phone like an idiot.
-Matt
Turn it off. Charge to atleast half or so battery. Boot into recovery, wipe cache, data, dalvik cache, and format system. Load up whatever ROM you want and only restore user apps and data.
Sent from my ADR6400L using XDA App
Just what he said but let google restore the contacts, this us unless you never allowed google to let th them sync.
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?
My pocket felt hot, so I pulled out my phone and saw that it kept rebooting itself. It just shows the initial Samsung splash for maybe a second or two, then loops again. I can get into Recovery and Download modes fine. I tried wiping the cache, factory reset, restoring a cwm backup. No luck so far. I've been using the CM9 rom for months. I haven't flashed or changed anything in months, I haven't even installed new apps in a while. Before this happened, it said I had no signal, so I had to restore my EFS(which I've had to do several times since I got the phone, mostly when I was switching back and forth from CM9 and stock to see which I prefer). After going into and out of airplane mode to reset the antenna, the signal and all worked fine. I let the phone cool down to make sure it wasn't just rebooting due to heat, but that didn't change anything. I've been searching here and google for anyone else with an identical issue, but I've failed so far. Everyone else seems to get to the home screen or just having random reboots during use.
Just to clarify, my question is: How can I fix my phone? Is there any other information I can give that would help?
I have the international i9300. I also tried removing the SD card and SIM card, since one thread concerning a different kind of rebooting issue reported success with that. Nope.
Try to reflash a stock rom on Odin
Is that different from restoring the original rom with CWM? I did that already. I don't have or know how to use Odin, but I'll download it and figure it out if that's the next step.
Solution?
Ok, I never didn't have to figure out Odin. I fixed it by wiping dalvik, factory resetting, restoring the stock rom, wiping it all again, rebooting into stock(it worked), then restoring back to the backup I made after the crash. Some of these steps might not be crucial, but at worst you waste a few minutes to make sure it works right again. Hopefully it'll help others with similar problems.
After flashing a new version of CM11, i found myself in a loop upon startup where many of the core applications of android stopped working. When i reverted back to the old version that worked(I didn't have a backup saved but rather i flashed the older nightly of the rom again), I noticed that my home button, lock screen, and notification bar/toggle screen wasn't working any more. I looked into it and looked at my apps, and saw an unnamed app with the description "com.android.keyguard". upon looking this process up, i found out that when people disabled this process their home button, lock screen, and notification bar stopped working (coincidental eh?), and decided that this was the source of the problem.
Is there any way to load on a new, fresh version of "com.android.keyguard" or should i just do a factory reset? I would prefer to save my local data, but if i must do it in order to have a phone that does anything useful, i obviously will.
If I need to do a factory reset, what is the cleanest and smartest method of doing so? I know titanium backup can cause a lot of problems (and in this case i'm worried it will duplicate com.android.keyguard), but I assume there is some sort of method that makes a factory reset while retaining the bulk of user data very easy. am i correct?
Do a full wipe and flash again, check the md5 of your download.
Only use titanium for use apps, never system apps or settings. There is no easier way to change rom.
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Jahid4 said:
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Click to expand...
Click to collapse
Flash back to stock and start over.
Beamed in by telepathy.
Hi guys ! Haven't found this thread anywhere so I had to ask.
When I installed a new Stock ROM everything was perfect, but as time went by, my wifi started to turn on slower and slower, now it takes him about 1 minute just to turn on. When I turn it on and go to Settings it just shows a blank page until the wifi turns on.
Please, DO NOT suggest:
1. Cache wiping
2. Safe mode and uninstalling previous apps
3. Wifi boosters
4. Advanced Wifi settings, special menu settings, turning of battery savings etc
Since I have tried all of those options
And yeah, everytime I reinstall a Stock ROM it works like a charm, but I don't have time to do it every 3-4 months just to make wifi fast as a lightning, as installing a new rom takes time and reinstalling all the apps makes me very nervous
Thanks for the answers, stay cool as always !
Other than using another kernel, not really sure what would help with that. I used to have an S4 and work on them often and hadn't seen that kind of thing before. Very odd behavior...
es0tericcha0s said:
Other than using another kernel, not really sure what would help with that. I used to have an S4 and work on them often and hadn't seen that kind of thing before. Very odd behavior...
Click to expand...
Click to collapse
I really have no idea what could it be, I recently factory reseted the phone and Wi-Fi worked again like a charm...
If the problem was kernel, can you recommend me how to find the appropriate one for my ROM and can I add it to the phone through ODIN without resetting the device ?
Thanks for the answer !
Post a screenshot of the About Phone section showing the Build Number of the software. That'll help determine which kernel to try. You'll need a custom recovery such as TWRP to install the kernel. Kernel installs are done through the recovery and only require wiping of cache and dalvik cache, not a factory reset. It's recommended to perform a backup in recovery to be able to restore if the kernel doesn't work or has adverse effects.
Here it is...will have to look up about thie things you just wrote on how to do it, cause I am a 100% dumbass for this