Hello,
I got a problem with editing file packages.xml (I need to fix problems with <shared user></ shared user>), because none of editings will survive a phone reboot. I tried the method using adb, which is described here and method using CWM also, but result is always the same, file packages.xml is restored to its previous original version after rebooting phone
Does anyone have any idea what am I doing wrong?
Thanks in advance for your advice.
VicC
Anyone got any solution for this?
Related
Hello, installed today an Alien rom, after powering on MoPho tries to register on sprint, and after that gave this error message "The Application SprintOmaDM(process com.motorola.android.sprintomadm) has stopped unexpectedly. Please Try again", i'm pushing a "Force Close" button and the registration process begins again with the same error. Tried other rom's with the same result. With the Please help me to solve this problem.
Ku4er said:
Hello, installed today an Alien rom, after powering on MoPho tries to register on sprint, and after that gave this error message "The Application SprintOmaDM(process com.motorola.android.sprintomadm) has stopped unexpectedly. Please Try again", i'm pushing a "Force Close" button and the registration process begins again with the same error. Tried other rom's with the same result. With the Please help me to solve this problem.
Click to expand...
Click to collapse
Try wiping your cache/dalvik cache and reflashing..I heard that helps when flashing new roms.
i have same issue...
after unlocking the bootloader...and flashing custom ROMs...
Re-wipe & Re-flash...still cant avoid activation...i tried it for many times!
seems that my photon will stay in Stock ROM...
Try this:
Remove or rename these files with Root explorer (you should already be rooted):
SprintOMADMConnMOPlugin.apk
SprintOMADMConnMoPlugin.odex
They are located in /system/app/ folder.
MultiDev said:
Try this:
Remove or rename these files with Root explorer (you should already be rooted):
SprintOMADMConnMOPlugin.apk
SprintOMADMConnMoPlugin.odex
They are located in /system/app/ folder.
Click to expand...
Click to collapse
Another android n00b here and I had the same issue trying to flash my photon for the first time, thanks for the info MultiDev, didn't fix the issue for me (as I cldn't get into the phones OS to remove the files in root explorer, it cycles network service and doesnt let you do anything else) however you put me on the right track so much appreciated! What I did (**do this at your own risk**)
Unzip the Alien-1.zip
Remove the 'SprintOMADMConnMoPlugin.apk' file from the /system/app/ folder
Rezip the files back into Alien-1.zip and re-copy to the sdcard
Clear caches and re-apply the rom
Hope this helps someone else as I was pulling my hair out b4 i stumbled on this thread...
I faced process.phone FC.
Hi there,
I upgraded my Galaxy 551 to Gingerbread 2.3.6. All went well. Unfortunately it seems to be a common side effect that the Z and Y keys (and some others) get swapped. The fix is apparently to modify the file /system/usr/keychars/sec_keypad.kcm.bin. The ideal thing is to put the old file from before the FW update back in, but of course I don't have that anymore! But the existing one can apparently be altered. If I can copy it to the SD card I can alter it in a hex editor and put it back.
So, I rooted my phone with that one click application, and that went OK too. I installed root explorer and found the file. There were also some others in the same folder I may be able to use. But, I cant make the folder R/W (pressing the button does nothing) so cant do anything with the file. I also tried Super Manager with no luck.
I am new to the phone fiddling stuff so noob level instructions would be appreciated!
Think I have it sorted. I installed superuser and then Root Explorer allowed me to select read/write. Now to try sort out this file!
OK, seems that you need to edit the file /system/usr/keylayout/sec_keypad.kl. Did that. DO'H now my keyboard doesn't work at all! Glad it saved a backup for me! Not sure what I did wrong, only edited two characters in a text file! Even the power button doesn't work. Got to pull that battery out LOL!
It seems when the file was saved it was saved with zero size. When I try to delete it to replace it with the backup it says cant delete, read only. So, not sure how I am meant to replace this and fix this problem.
Any ideas, remembering that I cant actually use any buttons on the phone!
I asked this in the general Q&A thread because I feel it is an android issue, not a Note issue...but alas no one even replied, trying it out here. Please help!
RockZors said:
Hello all,
I have a Samsung Galaxy Note i717. I have installed a few ROM's, but recently I installed CM9 unofficial build. After it was installed, I noticed that my default.prop is only like 4 lines long. So I try and add stuff to it (I am rooted, and used RW mode in Root Explorer). I can close the file and save changes successfully, but when I reboot it is back to the way it was with the 4 lines. It is not only that though, any files i add to the "/" get deleted upon reboot.
Things I have tried:
ODIN to stock rom, still did not have a full default.prop
Tried many different ways to change file system (different programs)
Ran fix permissions in CWM and busybox installer script
All with no success. Is there anything else I can try to fix this and be able to edit my "/" and have changes take affect. Or has anyone had this issue before?
Thanks
Click to expand...
Click to collapse
I was wondering if anyone with an i717 could go into cwm, run a backup, and upload that somewhere so I can restore it. Keep in mind your personal data gets backed up also, so preferably someone with a fresh working install. I don't care what rom it is either.
Thanks for reading.
The default.prop should only be 4 lines..
Are you confusing it with the build.prop?
Wow well don't I feel stupid. That's exactly what it was. Thanks for helping me see the way!
Hi! I have problem with my sd-card and have already tried my best to fix it but no result. When I delete, copy file to or even format my sd-card, it will return to normal.. nothing has been modified and all files can be opened as normal .. look like it doesn't save the state.. Have anyone met this? Hope you guys will help me to fix it!!
Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
positivehxcgo said:
Looking for a little help here.
In an effort to make some tweaks on my HDX, I somehow managed to delete the actual build.prop while I was in the process of trying to restore from a backup (build.prop.bak). I've tried removing build.prop.bak to build.prop, however Root Explorer keeps telling me that the Renaming Action has Failed.
I'm struggling to get my device to load/recognize on my PC with ADB. I'm looking for solutions to prevent my device from bricking.
Does anyone know if it would be possible to use the "Rollback" method from 4.5.3 to 3.2.8; or will not having a proper build.prop interfere with that?
The most aggravating thing, is I have a fully functioning build.prop backup, I just can't seem to get it to take as the actual build.prop
Any ideas are much appreciated
Click to expand...
Click to collapse
Sounds like you are on 4.5.3 but lost root. Might try to reroot using Kingroot although I believe that involves a reboot. Pretty sure your device will not restart (effectively brick) without build.prop. You really need to get adb working to expand beyond those options. Keep your device on charge to prevent a shutdown due to low battery.
I absolutely would not attempt a 3.2.8 rollback. There is an outside chance a factory reset from stock recovery would restore a generic build.prop if none is found. It generally will not repair or replace a damaged file and involves a reboot which could be fatal. This becomes an last resort option imo.
If you device was purchased from Amazon it may still be under warranty. Sometimes that is the best/only path. Good luck.
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
positivehxcgo said:
I've managed to get it mounted as ADB, and have pulled the backup, and renamed the file.
I'm now running into a problem pushing the file to /system/ I'm going to assume it's because I've lost my root access (I'm guessing it's because the buildprop manages it?).
So Making advances, just now stuck here. I've tried editing the prop, and it's in read only. I've tried sending it to a different folder and copying it over, but that's also failing.
Click to expand...
Click to collapse
You will probably need to root via adb which is challenging and by no means certain. Take a look at this thread for ideas. You may want to reach out to @myotai as he faced a similar problem.