So I rooted my device, hten followed a guide, that Instructed me to replace two files in the system/framework folder, services.jar and services.odex, i backed them up, but like a fool i backed them up in the same folder, which i can't access, I can restore from CWM and i was actually hoping someone had a system recovery that i could borrow, since i can't seem to figure out how to change the files back within my cwm backup.
callen2011 said:
So I rooted my device, hten followed a guide, that Instructed me to replace two files in the system/framework folder, services.jar and services.odex, i backed them up, but like a fool i backed them up in the same folder, which i can't access, I can restore from CWM and i was actually hoping someone had a system recovery that i could borrow, since i can't seem to figure out how to change the files back within my cwm backup.
Click to expand...
Click to collapse
Okay, slow down. You can fix this. There are only a few steps:
1. Download the stock odexed rom. You can find it here: https://www.androidfilehost.com/?fid=23622183712466565
2. Extract the stock rom.
3. Navigate to the system/framework folder
4. Copy services.jar and services.odex to your phone (download folder or anywhere on your sdcard is fine)
5. Since you are rooted, you can use a root file explorer to copy those files to your system/framework folder on your phone. Locate the two files you copied from the stock odex rom on your computer. Paste these into system framework, and overwrite the two existing files (you can use ES file manager or other root browser to accomplish this)
That's it! There are many other ways to do this, but this is probably the simplest.
I'd just flash a custom rom with hotspot though
Related
Quick question. It says put the file/folder in the root of your SD Card, Boot into recovery, then flash the zip file, for example Gingerbread Keyboard, but every time you boot into recovery, it just brings up Windows Mobile, help?
Gv2004 said:
Quick question. It says put the file/folder in the root of your SD Card, Boot into recovery, then flash the zip file, for example Gingerbread Keyboard, but every time you boot into recovery, it just brings up Windows Mobile, help?
Click to expand...
Click to collapse
There is no such thing as "Recovery" for us since we run off the SD card. You will have to use something like "Root Explorer" or something with root rights and copy and paste it to system>>app. Be sure to copy the lib that comes with the keyboard. That one will go into System>>lib. If you have any troubles you can PM me if you like.
P.S. Questions should go in the Q&A section, just a heads up man.
Forgot to mention. When I say copy and paste, I mean the actual app and lib that is inside the folder. You will have to unzip it first and you will see what I am talking about once you see it. One with say .apk at the end (which is the app) and one will have a .lib at the end which is the lib file.
I unzipped the file, I have a folder called "App", which as the .apk, and a folder called "Lib" which has the ".lib", so I want to copy and paste the .lib into system/lib, and the app in system/app, do I put both files on the root of my SD card first? and once I copy and past both into Root Explorer System/lib and System/app, what do I do next?
Gv2004 said:
I unzipped the file, I have a folder called "App", which as the .apk, and a folder called "Lib" which has the ".lib", so I want to copy and paste the .lib into system/lib, and the app in system/app, do I put both files on the root of my SD card first? and once I copy and past both into Root Explorer System/lib and System/app, what do I do next?
Click to expand...
Click to collapse
just reboot after that, infact just keep going on market and d/l a few things and it should update to the newer version itself, hope this helps.
just use titanium backup, I backed up the keyboard along with my apps so if I switched builds and it does't have the gingerbread keyboard, it will add it when do an app restore. One thing you have to manually select the keyboard from the app list, long press and backup.
just do an adb push it is the easiest way.
download the gingerbread keyboard (LatinIME.apk) and the lib file (libjni_latinime.so)
(assuming you have the sdk installed and you have usb debug turned on)
in command prompt, navigate to the folder that contain these two files.
then type: adb push Latinime.apk /system/app/ (press enter)
then type: adb push libjni_latinime.so /system/lib/ (press enter)
then you should have the new keyboard installed!
I am trying to take a keyboard that somebody made into a flashable .zip file, and implement it into a rom that I am working on. What I did was flash the .zip through cwm, then found the apk, backed it up, and then placed it in the /system/app folder on the new rom. The problem is as soon as the rom boots, I get a force close error. So I took a look at the .zip file, there are two folders meta-inf and system. inside system there is an app folder and lib folder. My question is can I just take the apk and lib file out and place them directly into /system/app and system/lib on the new rom? and if so do i need to do anything with the META-INF folder? any ideas would be GREATLY appreciated!!!
thanks
the META-INF folder may have some script that does some other manipulation of the filesystem or runs helper apps during installation. See what's in META-INF/com/google/android/update-script.
Hi I created a bootanimation and want to make it flashable. I followed tutorials from the net and xda. I got two files META-INF and system.
I put my bootanimation.zip in system/media. That's all. I didn't touch META-INF .
After flashing the zip in cwm, it says Installation aborted . Need Help please...
thats because the flashable zip wasnt for your phone
status 0 - wrong update binary
status 6 - wrong update script
here is my template for you
simply download it
open it in winrar (or if using phone just unzip everything)
open the system foler
you will notice a framework folder that is currently empty
you can leave this folder as it is
just create folders to where you want to flash the file to
for example your bootanimation.zip create the following
in the system folder create a folder called media
in the media folder place your bootanimation.zip
the same is true for any other files you want to flash
if you want to flash a file to system/framework just put a file in that folder
if you want to flash a file to system/app just create a folder called app in the system folder and put what you want to flash there
if on winrar you just have to open the zip and right click and create a folder - no need to unzip everything
if on phone and you have unzipped everything just zip everything back up when done
flashable zip template can be download from here
if you are using stock rom you need to enable custom boot animations first using the custom boot enabler zip
(if you already have a custom boot animation and bootanimation.zip working in a custom rom then you dont need to do this)
Ovafloa_X said:
Hi I created a bootanimation and want to make it flashable. I followed tutorials from the net and xda. I got two files META-INF and system.
I put my bootanimation.zip in system/media. That's all. I didn't touch META-INF .
After flashing the zip in cwm, it says Installation aborted . Need Help please...
Click to expand...
Click to collapse
If just a bootanimanion, push using root browser only
Or using a another flashable bootanimation file and the replace the bootanimation.zip with yours
I attch it . Credits to its maker
works perfectly! thanks
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Icculus760 said:
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Click to expand...
Click to collapse
Follow these instructions. Enjoy.
Misterxtc said:
Follow these instructions. Enjoy.
Click to expand...
Click to collapse
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Icculus760 said:
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Click to expand...
Click to collapse
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Misterxtc said:
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Click to expand...
Click to collapse
What the heck, man. Stop helping me so quickly! :laugh:
Thanks again!!
I recently flashed the stock android lollipop tgz file on my nexus 7. I rooted it, and then wanted to restore my nandroid backup. But, the backup does not appear in the recovery menu. I couldn't also copy the backup files to the tarp folder (no such folder existed, and when I tried making one using es file explorer or root explorer, it gave an error message.) How do I fix this problem. Please help guys I am sort of new to the forum[emoji16]
Same problem here. It does show up but it's a 0 bytes file last modified in 1970 (start of unixtime)
This is on my Nexus 4 though. Flashed manually with official images from Google and rooted with SuperSU.
- make sure you're using the latest twrp recovery for your device. get the latest img file for grouper (nexus 7) and mako (nexus 4) here: http://techerrata.com/browse/twrp2
- if you look around the forums, you'll find that people have had similar issues since lollipop. forget about trying to access twrp folder in android/es explorer for now (BTW droiderrr18 is probably getting the error when trying to create the folder because it's already there, just doesn't look like a folder and can't be opened, it looks like the 0 byte file looking thing LooieENG mentioned).
What you want to do instead is boot into twrp recovery and connect to your computer. you should be able to access your folders and files in MTP connection from Windows and move to your old backup that way. if not you can always use adb push command. the backup folder for twrp is storage/sdcard0/TWRP/BACKUPS
you can also do a new backup and find it, then move your old backup there to restore.
(side note: twrp also has its own file manager where you can see and if necessary manipulate your files, but be sure you know what your doing in there)
dtg7 said:
- make sure you're using the latest twrp recovery for your device. get the latest img file for grouper (nexus 7) and mako (nexus 4) here: http://techerrata.com/browse/twrp2
- if you look around the forums, you'll find that people have had similar issues since lollipop. forget about trying to access twrp folder in android/es explorer for now (BTW droiderrr18 is probably getting the error when trying to create the folder because it's already there, just doesn't look like a folder and can't be opened, it looks like the 0 byte file looking thing LooieENG mentioned).
What you want to do instead is boot into twrp recovery and connect to your computer. you should be able to access your folders and files in MTP connection from Windows and move to your old backup that way. if not you can always use adb push command. the backup folder for twrp is storage/sdcard0/TWRP/BACKUPS
you can also do a new backup and find it, then move your old backup there to restore.
(side note: twrp also has its own file manager where you can see and if necessary manipulate your files, but be sure you know what your doing in there)
Click to expand...
Click to collapse
I have the same problem. I need to access its data.f2fs.winxxx files for restoring my backed up apps using Nandroid Manager, which cannot access the folder, even though the original folder (/data/media/0/TWRP) can be accessed from ROOT EXPLORER and TWRP recovery file system
Nandroid Manager looks for only /sdcard/TWRP directory i guess, thus is unable to get backup storage location. Changing the Storage location in Nandroid Manager also has no effect.
I need to restore my backup apps. Please help if u can!