Hello.
Something gone wrong with my backup, the app_process.orig wasnt created, system status is modified and long story short i would like to get app_process to its original form.
So my question is : Is there a way to manualy remove changes done to app_process by xposed instaler? Or any other way to get it back to stock?
If your device is bootlooping:
If you have the ROM of device, you can extract
Code:
/system/bin/app_process
and push to your device.
Given that your device's USB debugging was on. If it wasn't, you can copy the app_process file in your sdcard and flash Aroma File Manager in recovery mode and copy it in right place and set permissions.
If your device isn't bootlooping:
You can use any root file explorer to copy that in right place.
Related
This is a script that I made for my own use awhile ago because I couldn't find an OS X deodexer. I recently modified it for use with Linux, and if you're on Windows and have Cygwin, well, it works with that too.
What is it:
It's a generic deodexer, for any ROM, and theoretically for any recent phone. What do I mean by theoretically? Well, the Atrix is my first and only Android so far, but I expect to be able to use it when I get others It should work with any phone that has all its framework in /system/framework and all its apps in /system/app. Any phone that doesn't have that doesn't qualify.
How does it do it:
It uses the phone's own BOOTCLASSPATH and patches together any additional necessary dependencies from /system/framework. It then uses the phone's own files to create the deodexed frameworks and apps (via JesusFreke's baksmali/smali). All the other deodexers I've seen use canned files that have been created ahead of time, or require you to specify the proper dependencies for your phone. This is fully automated and requires almost no intervention on your part. This means you don't have to go looking for "the right" deodexed files for the new stock ROM you just flashed, or know anything about dependencies. All it asks for is Super User permission at the very start (which you need to allow and check "remember", because it will need it later).
When will it be done:
In about a half hour from when you start. At least that's how long it takes on my Core2Duo 2.53Ghz, 4GB RAM MB Pro. There are 250+ files to decompile and recompile. It's a lengthy process.
Prerequisites:
1. You must be rooted with Super User installed.
2. USB Debugging must be turned on on your phone. Settings > Applications > Development > USB Debugging.
3. You need Java on your computer, and it has to be in your path (you can test by opening a terminal (or cmd for win) and typing 'java' on the command line. If you see help for that command, you're good).
There are 3 scripts:
1. deodex.sh: This is the main deodexer script. Run this to deodex a ROM for the first time. It will do its thing, and once it tells you it's rebooting, you should be deodexed.
2. postcompile.sh: If you restore to a non-deodexed state somehow and you have run deodex.sh previously on the same ROM, you can use this to skip the lengthy compiling and just deodex with the files you already created (they will be in framework.out and app.out on your computer).
3. restore.sh: Use this to return your phone to an odexed state. Obviously, you have to have used deodex.sh to deodex first.
After running deodex.sh, you may want to zip up and save framework.out, app.out, and the system folder in the deodex folder. These contain the deodexed files and your original files for the current ROM. If you ever want to use the restore or postcompile scripts, you need these.
please help
line 15: ./bin/osx/adb: No such file or directory
Error in previous command above line 18.
Exiting.
logout
cyrux said:
please help
line 15: ./bin/osx/adb: No such file or directory
Error in previous command above line 18.
Exiting.
logout
Click to expand...
Click to collapse
Interesting, either it's saying you have no /data/tmp folder on your phone, or you're missing ./bin/predeodex.sh.
Are you able to check if your phone has a /data/tmp folder? Also, a step I forgot in the OP. Do you have USB Debugging turned on?
*edit* Okay, so I downloaded my zip from here just to be sure, and tested only the section you're having trouble on by making it quit out right after the part you error'd out on. I've verified that predeodex.sh is working, so /data/tmp must be missing on your phone?
My motherboard is toast, I bought a broken phone on ebay and switched out the motherboards but it isnt working. Phone works fine but wont recognize sim card or connect to network. Its just a camera/wifi device atm. So anyway..... I can still get the old motherboard to kinda work enough to play with it, the home buttons dont work or the power button and sometimes freezes up. Is there a way I can put the old motherboard in the phone and copy the system files to the external sd card or computer, then wipe the new motherboard and copy the files from the old mb to the new mb? I believe I have tried everything else but if anyone has any suggestions Im all ears
Thanks!
The easiest way would probably be to take the motherboard you're wanting to pull stuff from, hook it up (in the phone), and via USB in ADB do something like this:
adb pull / \backup
That would create a folder at the top level of your C: drive with all the contents of the phone on it. You could then move all of that to the new motherboard.
(That would probably be something like:
adb push \backup /
but I'm not 100% sure on that. You may have to do a more one-by-one procedure.)
when I try to push the backup I get this message....
failed to copy '\backup/acct/uid/0/task' to 'acct/uid/0/task' : Operation not permitted
Sooooo what did I do wrong??
Also I couldnt find where it saved the backup on my computer.
Ok, found the backup folder on my c: drive but what do I do with it now?
Bump cause I still havent figured this out Seems like I dont have the correct permissions in adb.
poprocksncoke said:
when I try to push the backup I get this message....
failed to copy '\backup/acct/uid/0/task' to 'acct/uid/0/task' : Operation not permitted
Sooooo what did I do wrong??
Also I couldnt find where it saved the backup on my computer.
Ok, found the backup folder on my c: drive but what do I do with it now?
Click to expand...
Click to collapse
If you typed in your backup like what you wrote above (\backup/acct/uid/0/task), it's likely that you're running into an error because you flipped your slashes midway through.
The backup folder needs to be in the platform-tools folder of the ADB installation, as that's where ADB pushes from.
Once you have that, reboot into recovery mode. This may not be 100% necessary, but I usually find that pushes work better from there as the file system is (usually) read-write.
Then, try this:
adb push \backup /
(You may have to switch the slash before the word backup so it reads /backup, I'm not 100% sure.)
If that doesn't work, drag an individual folder out of the backup folder to the main platform-tools folder and type:
adb push /acct \
You'll have to repeat that for each folder, but it should work.
If all that fails, you can try to make a CWM flashable zip file. I don't know exactly what the procedure is for doing this, but I would guess that the answer exists somewhere on this site.
jmtheiss said:
If you typed in your backup like what you wrote above (\backup/acct/uid/0/task), it's likely that you're running into an error because you flipped your slashes midway through.
The backup folder needs to be in the platform-tools folder of the ADB installation, as that's where ADB pushes from.
Once you have that, reboot into recovery mode. This may not be 100% necessary, but I usually find that pushes work better from there as the file system is (usually) read-write.
Then, try this:
adb push \backup /
(You may have to switch the slash before the word backup so it reads /backup, I'm not 100% sure.)
If that doesn't work, drag an individual folder out of the backup folder to the main platform-tools folder and type:
adb push /acct \
You'll have to repeat that for each folder, but it should work.
If all that fails, you can try to make a CWM flashable zip file. I don't know exactly what the procedure is for doing this, but I would guess that the answer exists somewhere on this site.
Click to expand...
Click to collapse
Actually what I typed was adb push \backup / then it gave me that error. It stored the backup folder on my c: drive, I will move it to the tools folder and see if that works. Going to go search on how to make a CWM flashable zip file now. Maybe i'll give that a shot too. Thanks for your help.
So If I am getting this correctly, I take the custom ROM I have flashed to my phone and then I can add my system files to to the system folder in the ROM I can then flash the ROM again and it will install all my files?
In theory, yes, that should work. All the CWM update file does is write the files inside of it to the folders that the updater-script file tells it to.
Again, this should work IN THEORY.
poprocksncoke said:
So If I am getting this correctly, I take the custom ROM I have flashed to my phone and then I can add my system files to to the system folder in the ROM I can then flash the ROM again and it will install all my files?
Click to expand...
Click to collapse
Ok, I tried this and put the .zip on my sdcard and ran it from recovery. Got an error that I didnt have enough space. Any suggestions?
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
aerosmike said:
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
Click to expand...
Click to collapse
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
alray said:
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
Click to expand...
Click to collapse
Thank you very much
tried this mod: http://forum.xda-developers.com/showthread.php?t=2512981 in order to get tethering to work. It didn't.
I overwrote framework-res.apk in the system/framework folder with the one in the mod. I did backup my original .apk file into a folder I made off the system folder.
I am rooted with towel on 4.3
Now my phone goes to an AT&T logo screen and stays there. Is this what is considered a soft bricking? Is there a way to browse the files from my PC and overwrite the mod .apk file with my backup or any other method to get back in there and overwrite the file back to where I found it?
can you get into download mode? if so, just reflash the lot with odin.
The custom rom I am using on my device for some reason doesn't have logcat. After a bit of digging up in the root folder, I found out that it was missing logd file which should be present under /system/bin and is necessary for logcat to work. Already tried to copy it from the official rom of my device (I extracted it from system.img) but pasting it manually (tried both a root explorer and adb) in /system/bin won't do anything as any changes made to /system/bin get reverted back automtically after reboot.
So I thought of a method about hooking Runtime.loadLibrary with xposed and redirecting it to logd on my internal storage when it's requested. Isn't that possible ?
Otherwise, do you suggest any other solution?
Do you think I should move the file with twrp if this doesn't work ? (I am avoiding the use of it because it's still unstable for my device and bootlooped a few times.).
Or should I edit the custom rom's system.img and repack it (I'm afraid if it's size changes my device won't boot)
I will be very grateful if someone helps me out
if you copy a file you must set right permissions and ownership