Hi,
I just made my SGS boot looping by editing some settings in /data/data/com.android.providers.settings/databases/settings.db. CyanogenMod came back with FC loop of the Phone app so I deleted 2 entries from the db. Before that I (thought I) made a backup of the settings.db. After the Phone's FC was gone I replaced the edited settings.db file and rebooted (since I did not like the changes to Status Bar Widget Buttons). Now I am stuck in a boot loop. Reflashing the rom does not help.
Does anyone have a hint on this? I am trying to avoid wiping as long as I can.
Thanks a million.
Now this is a little embarassing. I just renamed the settings.db to settings.db.bak while it was boot looping. The file was immediatly recreated and the phone booted without a glitch.
I'm having the same problem. How did you get yours resolved?
Edit: I see the red writing now. I wonder how you edited the file while it was in the boot loop. Using adb maybe?
Edit #2: Using shell commands. Now I got it. Lots of google searching.
Related
Hello everyone.
I have been searching for hours and found nothing relating to my specific issue. Basically it is this, I have recently finished a theme and am ready to release it. Before doing so I wanted to test its functionality. Now pushing the apk's through android commander works perfectly, installing my themed apk's via update.zip through recovery has become a headache. After the "update" has finished and I boot the phone i run into an interesting scenario. Once I slide to unlock I get an error that com.phone.apk is fc'ing then boot loop. Same error until I pull the battery. I have no idea wtf is going on and I came here to you fine folks searching some assistance. Btwi haven't touched the phone apk. Here is what I themed:
ADW
Browser
Google quick search box
MMS
Settings
Framework
All the above are directed to system in the update script.
I also included two widgets that I made and directed those to data.
Script looks like this:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
Now this is my first time doing this and from everything I have read this will do what I want, and for the most part it seems as if it has copied the right files but somehow in the process fubared other things.
Any ideas, help and solutions are greatly welcome.
Syn
Hi.
I have a problem, which I don't know how to solve.
Of course I had a root. I have installed busy box and trickster MOD in order to disable 3D scaling to boost some games like NFSMW (Actually, it worked!).
With no rebooting I tried to delete PlusOne.apk and PlusOne.odex from system/app to speed my phone (this app running in the background all the time usses the memory). I used Total Commander mounting R/W, but didn't unmount it.
Next I rebooted my phone.
First, it was stuck on Upgrading Android - optimizing apps (i see it for two seconds on every normal boot, so I thought it may take longer this time but after 10 minutes nothing happened). I tried to do a hard reset, and afer doing it, now, the phone is stuck on lg boot animation.
Could you help me solving the problem? Please tell me what was the problem that I can avoid it in future.
DidierDrigbi said:
Hi.
I have a problem, which I don't know how to solve.
Of course I had a root. I have installed busy box and trickster MOD in order to disable 3D scaling to boost some games like NFSMW (Actually, it worked!).
With no rebooting I tried to delete PlusOne.apk and PlusOne.odex from system/app to speed my phone (this app running in the background all the time usses the memory). I used Total Commander mounting R/W, but didn't unmount it.
Next I rebooted my phone.
First, it was stuck on Upgrading Android - optimizing apps (i see it for two seconds on every normal boot, so I thought it may take longer this time but after 10 minutes nothing happened). I tried to do a hard reset, and afer doing it, now, the phone is stuck on lg boot animation.
Could you help me solving the problem? Please tell me what was the problem that I can avoid it in future.
Click to expand...
Click to collapse
due to the fact that you've played around with your /system/ partition, you've got to reflash stock again...
So, what to do?
laufersteppenwolf said:
due to the fact that you've played around with your /system/ partition, you've got to reflash stock again...
Click to expand...
Click to collapse
So, i have to flash the kdz ROM using this tut: http://forum.xda-developers.com/showthread.php?t=2069723 ?
I understand that deleting anything from there is not a wise idea, I won't make this mistake again?
But not unmounting r/w after mounting it, is ok? Nothing should happen if I didn't delete those files from system partition?
DidierDrigbi said:
So, i have to flash the kdz ROM using this tut: http://forum.xda-developers.com/showthread.php?t=2069723 ?
I understand that deleting anything from there is not a wise idea, I won't make this mistake again?
But not unmounting r/w after mounting it, is ok? Nothing should happen if I didn't delete those files from system partition?
Click to expand...
Click to collapse
first, yes, you've got to reflash via kdz
second, of course you can delete stuff in /system/ partition BUT you need to know what you are deleting e.g. deleting SystemUI.apk is no good idea at all you can find a "safe list" here on xda in general section
third, unmounting is a part of the shutdown process, so it happens automatically i for one never unmounted anything
Hello guyz,
I think so I have messed up the system file while doing some modification.
I was trying to add the on screen navigation key command to build prop. But the problem started when I tried to replace the original build.prop file when I found the command which I added for on screen button was not working. So I just simply replaced the backup file and rebooted the phone but It got stuck at the LG logo.
I am able to boot into recovery but I don't know what to do now.
Please help me out I don't want to loose my data.
Thanks.
I resolved the issue. I changed the file permission and it worked.
mods can close this thread..
kernel.debugger said:
I resolved the issue. I changed the file permission and it worked.
mods can close this thread..
Click to expand...
Click to collapse
Can you please explain further in detail how you fixed this? I am having the exact same problem.
Ok, I dun goofed. Phone was working fine but I tried to add a line to build.prop and now the phone will show the boot logo but then goes black. I made a copy of the file first and tried putting the old one back with the TWRP file manager, but it's still doing the same thing.
I need help with this fast, my gf is going to kill me if I don't get he phone working again soon. :/
Can someone post a flashable zip of the 5.1 build.prop please. I'm just assuming this will fix it. I've tried extracting the system.img to get it but I obviously don't know what I'm doing.
Thanks
PROBLEM SOLVED!!!!!!
After sitting here with high blood pressure for 45 minutes I fixed it. I just pulled and pushed the files with ADB. I guess using ES file explorer to play with system files is a big NO. Lesson learned. :/
I'm sure this is the right spot since it has to do with troubleshooting. Okay here goes, so I've looked in a lot of places in the nexus 6 and Samsung sections and cannot find any info on how to remove the binary for Samsung devices (I know, let me explain first) to be able to boot animation screens.... So, let me back up a bit and explain why I'm an idiot. I've been using rom installer to install boot screen animations for my rooted nexus 6 with 6.0.1 Marshmallow. Well, I noticed that some were the incorrect size for my phone when I installed them. I had noticed an option in the app under room extras to install binary to allow boot screen animations (boot animation fixer). I was in such a hurry that I didn't notice that right above it said Samsung. I foolishly installed it, it rebooted and now the boy animation is a plain Jane google writing in white with no animation. Can't remove it or revert to backup because all my backups got corrupted somehow. So now I thought if I can reverse this somehow by deleting the binary, or script, or whatever, it will fix it. I did research on the app and can't find out where it installs the binary to. I came on here and looked in the Samsung section as well as the nexus 6 section, which led me to ask for help. I've looked where the boot animations are stored on the system and there's nothing there and I'm worried if I dig anywhere else blindly I'll have to wipe and install 6.0.1 and root all over again, using up a LOT of my data to reinstall a LOT of apps that I have. I have like 239 apps so I would like to make that a last resort. The phone boots fine, I just don't like the bland boot animation. I want to show off the different animations that I use. I would appreciate the direction anyone could lead me in to solve this goof up that is my fault, but hey, I'm learning a lesson here.
EDIT: I forgot to mention that I did find the XDA forum on the binary samsungani related to this (/system/bin/samsungani) and the boot animation binary (/system/bin/bootanimation) and deleted them. However, this did not change a thing.
I mean, as long as you're able to boot up, why not just install Titanium Backup and backup the apps. Reinstall your rom and just restore the apps, I would say that would be an easier fix. That way you won't be using any data.
The problem is, as you yourself found it, the bootanimation.zip is missing. Copy one in system/media, give 644 as permissions (rw-r--r--). And there you are.
Sent from my Nexus 6 running cyosp using Tapatalk