Hi everyone! I'm still relatively new to all these customizations that can be made on these phones, and I am curious about all these .apk files I keep seeing around. Everyone time one is posted, it says to push it to your phone to replace whatever file is there... The thing is, every time I read about it I find a new way of doing it. Some say to use root explorer, some say SGS tools app, some say to use easy installer, and I think I've even read to use ADB? I just was wondering what's the best method? Easiest method? Can you screw your phone up by replacing these files? I keep reading things like if you want to switch a camera in your ROM to a different version, just install the .apk! Or, if you want to use live wallpapers in a ROM that doesn't come with it, here is the .apk for that!
Any help is much appreciated!
Thanks guys!
tarastaryo said:
Hi everyone! I'm still relatively new to all these customizations that can be made on these phones, and I am curious about all these .apk files I keep seeing around. Everyone time one is posted, it says to push it to your phone to replace whatever file is there... The thing is, every time I read about it I find a new way of doing it. Some say to use root explorer, some say SGS tools app, some say to use easy installer, and I think I've even read to use ADB? I just was wondering what's the best method? Easiest method? Can you screw your phone up by replacing these files? I keep reading things like if you want to switch a camera in your ROM to a different version, just install the .apk! Or, if you want to use live wallpapers in a ROM that doesn't come with it, here is the .apk for that!
Any help is much appreciated!
Thanks guys!
Click to expand...
Click to collapse
You CAN screw your phone up if you do it to the wrong APK (like /system/framework/framework-res.apk, if you install a bad one, your phone won't boot, but there is an easy fix, nandroid!).
Basically all the methods do the same thing. In Android "Installing" an app is as easy as moving it to the correct location. All of these methods do just that.
The easiest way IS to probably use Root Explorer because you can rename the old one just in case, and it will handle the system read/write mounting for you. Plus GUIs are always easier.
So here's how it works: user apps go in /data/app, and system apps go in/system/app. User apps can't really mess anything up, but be careful with System ones. Live wallpapers, things of that nature usually don't hurt. Camera is ok to mess around with, too.
Edit: my ramblings are probably confusing, don't hesitate to ask me to clear something up
usually most apk files can be installed easily by transferring the file to the root of your internal sd card then go to MY FILES locate the apk file and click on it and it will ask you to install. Thats it. You can also root explorer and just place it in the system/app folder then reboot. I install all of my apks through the first way I mentioned. On my wife's Mytouch4g there is no my files so use Astro file manager. Come to think of it any file manager from the market will do. Good luck...
tarastaryo said:
Hi everyone! I'm still relatively new to all these customizations that can be made on these phones, and I am curious about all these .apk files I keep seeing around. Everyone time one is posted, it says to push it to your phone to replace whatever file is there... The thing is, every time I read about it I find a new way of doing it. Some say to use root explorer, some say SGS tools app, some say to use easy installer, and I think I've even read to use ADB? I just was wondering what's the best method? Easiest method? Can you screw your phone up by replacing these files? I keep reading things like if you want to switch a camera in your ROM to a different version, just install the .apk! Or, if you want to use live wallpapers in a ROM that doesn't come with it, here is the .apk for that!
Any help is much appreciated!
Thanks guys!
Click to expand...
Click to collapse
An apk is a specialized application file used by android (uses the same file headers as .zip files).
You are correct that there are various methods to push or move apk's to appropriate directories with in the phone. now as to which is easier or best, all methods work about the same, though there are minute differences.
If you want to move apk's into a certain directory while using a phone i find it easiest to use a file manager like root explorer that has root permissions to move apks around. keep in mind that when moving system files most often you will have to reboot for the changes to take effect with out bugs.
If instead you want to use a computer personally i find ADB to be the easiest. After installing the android sdk you will have to navigate into the android sdk directory then to the platform-tools directory within the android sdk folder. then in command prompt type " adb push <directory of file on your computer> /<directory of where you want it on your phone> hit enter and all is gravy. keep in mind that pushing/moving files to your phone using adb works the best when in recovery mode.
as to which of these operations is the best is a personal decision personally i like to use adb to move around system files and root explorer for applications.
hope this helps
Thanks guys!! Ok, so just to be sure. I'm currently running the Malice rom, and somewhere in the threads is the LiveWallpaperPicker.apk
So all I have to do is download this, place it on the root of my internal SD card, go into file manager and find it, click on it, and it will ask me to install it? It's really that easy??
Or, should I download root explorer and copy and paste it to a specific place?
tarastaryo said:
Thanks guys!! Ok, so just to be sure. I'm currently running the Malice rom, and somewhere in the threads is the LiveWallpaperPicker.apk
So all I have to do is download this, place it on the root of my internal SD card, go into file manager and find it, click on it, and it will ask me to install it? It's really that easy??
Or, should I download root explorer and copy and paste it to a specific place?
Click to expand...
Click to collapse
For that file you will need to place it in /system/app (it can't be installed normally because it's a system app). So you need something like Root Explorer
I think EStrongs File explorer is a decent free alternative, but when I tried it a couple months ago I had no luck with it so I just bought Root Explorer (good investment)
The guide in my signature touches on this, but BT has you covered. I am also a huge advocate of Root Explorer.
Just take the .apk, move it to system/apps and I reboot, but it may not be necessary... no need to click on it and select install, as BT referenced.
Thanks so much everyone! Just purchased root explorer and will try this out.
IT WORKED IT WORKED IT WORKED!!!!!!!!!!!!!!!!!!!!
After I rebooted, none of my widgets could load, but I have live wallpapers again! I love learning new stuff! Thanks sooooooooooooooooo much! You guys are the BEST!!!
Odd about the widgets. Were you able to just remove them and re-add them back?
Yep, just deleted them off my home screen and added them back again. All of them had errors saying widget could not load
Related
There is a font on another rom that I like, how would I get that installed onto my Eris? I have the file from the other rom.
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
bftb0 said:
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
Click to expand...
Click to collapse
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
johnny quest said:
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
Click to expand...
Click to collapse
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
bftb0 said:
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
Click to expand...
Click to collapse
Ok, thanks I will give it a try.
johnny quest said:
Ok, thanks I will give it a try.
Click to expand...
Click to collapse
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
johnny quest said:
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
Click to expand...
Click to collapse
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
bftb0 said:
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
Click to expand...
Click to collapse
Thank you so much, I've been living on backups and restores. believe me I've learned my lesson. I will give this a try.
Your method worked great with the Root Manager. I bought it on the market. Ok, my biggest problem now is that my font is microscopic small. I don't know why. But I can't see the letters of which folder I'm in to take that font out.
I need a favor: can you post up screenshots or the number of folders to scroll down to get to the system/fonts/droidsans.tff
I can't see it, really its that small its the universal acc font.
Never mind I got it. Took a lot of squinting but I got it. Thanks.
Here is the correct way to use root explorer for manually replacing system files:
1. Mount the system as r/w (read/write) per the top right corner. Navigate to the file that you plan to replace (e.g., system/framework/framework.jar).
2. Copy (not move) the file and paste it somewhere on your SD card (internal or external, doesn't matter - as long as you can locate it in case you need to put it back). Rename the file you just pasted, but very subtly. For example, when renaming framework.jar, I would only throw something in front of the file name, such as "Backup - framework.jar", so I can easily distinguish it from the new file if I put them in the same spot.
3. NANDROID BACKUP!
4. Download/put on your sd card (whatever you do) the new file that you want to replace the old one with.
5. Move the new file to /system (not in a subfolder yet). Here you will change the permissions, which is crucial to avoid FCs and problems. In root explorer, you would long press the file, press permissions, and set them to whatever the old file's permissions are. This may require going to verify what they are before starting this step. For example, in a lot of cases, the permissions will be RW-R-R. In Root Explorer, this would mean checking the first two boxes on the first line and only the first box on the next two lines. In any situation, confirm that the permissions you see after you've changed them (right below the file name) match exactly what you're replacing.
6. Ensure that your new file is correctly named to exactly what it is replacing (case actually matters) and double check the permissions.
7. Move your new file to the folder, root explorer will ask if you want to replace the file. Confirm.
8. Back out of root explorer and immediately reboot.
No force closes, no problems .
It may seem like a lot to someone who doesn't do it often but for me, I actually do this method faster than any other and fly through it every time. I got tired of seeing people explain ways to use Root Explorer which result in bootloops, FCs, etc. without fail. So, I decided to put an end to it.
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Audiochild said:
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Toggle "Mount R/W" button at the top.
Audiochild said:
Great post Simba501! Thank you for this...
Obviously a "noob" thing I'm over-looking but when I try and paste the file I'm moving into /system it's prompting me that it's "read-only"?
Click to expand...
Click to collapse
Sounds like you need to mount \system as read-write. There is a button in the upper right corner of root explorer to mount
Sent from my SGH-I777 using XDA App
Thanks wonner and kbilly70! That was the issue
Awsome. Bookmarked!
thanks for the awesome guide. worked great for me!
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
kZard said:
Thanks, that clears things up.
I'm still wondering, though, how does one handle certificate files etc? For example, the ones found in this fix provided by zdzihu, in the META-INF folder.
Click to expand...
Click to collapse
Those are only for flashing purposes. Not needed if you're not flashing it. You only need to pull everything besides that folder and place them appropriately.
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Edgarhighman said:
Using this method resulted in "app not installed" tried it with black Google search box, and just now with Mms.apk rw-r--r-- backed up old one, but method didn't work... had to nandroid last time because phone wouldn't let me install backup or market version. Looks like I'm in for it again. fudge. what went wrong?
System folder was r/w and moved apk into system/app said OK to overwrite and used hard key back button to exit root explorer. Hard key power button and selected reboot within 1-4 seconds of moving apk over system app.
Click to expand...
Click to collapse
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Simba501 said:
You don't install it after placing it. Placing it in the folder does install it. If you put it there, ensure the permissions are correct, and reboot, it should work.
EDIT: I don't see any mention of setting the permissions, so that was probably the issue. Again, no need to "install" it; just put it in the appropriate folder and set the permissions.
Click to expand...
Click to collapse
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Edgarhighman said:
I did state the permissions. It's in your quote lol. Your method caused my phone to say app not installed. I had trouble getting the default app back after your method failed. Why didn't it work? I'm telling you I followed it to a T.
Sgs2, android 2.3.6, unnamed rom, December 2011 entropy kernel
Click to expand...
Click to collapse
If the apk is compatible, it will work. At no point should you get an "application not installed" prompt, unless you attempted to manually install it at some point. If it wouldn't work, it just wouldn't appear in the app drawer: no prompt.
I guess this should be mentioned in the OP, but some times, clearing data of the application may be necessary after finishing. Usually a force stop at the most will allow you to see changes (which is why the steps include a reboot). You've piqued my interest. Post the files of question and I'll see if they work on my device. There was a similar issue someone else was having; I told him to redownload the apk and that was the problem. Some kind of botched file/download.
Sent from my Galaxy S II (i777)
can you edit or create new folders in the /sys directory?
mikoal said:
can you edit or create new folders in the /sys directory?
Click to expand...
Click to collapse
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Simba501 said:
No. Why would you want to?
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
mikoal said:
just wondering what the limitations of root explorer are.
is it only that folder? and why that folder?
Click to expand...
Click to collapse
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
dsmboost said:
You can edit and create new folders in that directory, but there's just no need to, unless you want to break the functionality of your phone.
Click to expand...
Click to collapse
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Simba501 said:
Idk: that's the only one I've seen. I've created folders in other directories. At any rate, virtually every modification you'll ever make will be in /data or /system.
It fails if attempting to create it within Root Explorer. You could use other means though (on a PC, an edited ROM zip, or potentially another root file manager). But again, no real reason to: other than for development purposes, perhaps. I'm no developer though, so I can't say.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
Ah okay, I was referring to ES file explorer, which can modify other files in that directory.
thanks to you both!
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Well presumably this is how ROM Manager and Metamorph both do their thing, just in a slightly more round about way (as they don't come with the files they need to copy). I'm almost 100% sure this is possible, but I've never tried it personally.
EDIT: Looks like this is how you'd do it: http://developer.android.com/reference/java/io/File.html. Specifically the renameTo() method.
CelticWebSolutions said:
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Click to expand...
Click to collapse
Well there are about a dozen ways to do this. First of one of the hardest things is comming up with the commands/script. I can defiantly do this. If you want an apk, there are a few guys whom could port my script to an apk. I'm going to make a script here that will format, and create partitions and extract directly from the nook, no need to go through the fancy formatting and such, just go into terminal and run the script. Ill post a prototype for you to have the testers test!
Do you think something like BacksideUpdater inside custom ROM for LG Optimus V?
made by JerryScript
JerryScript i very nice guy, I bet if you ask him, he will let you play with his code
if is it what you looking for
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
xdajunkman said:
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
Click to expand...
Click to collapse
So one of the problems is its not really copying. Its more of an extraction from one place to another. We are required to use dd, and fdisk(for formatting).
GREAT! I was worried updates would be to complicated for people
Sent from my Nook Tablet using xda premium
... and I was worried that I might have to wipe my NT clean again to get the updates. After a week with this wonderful upgrade, I've got a LOT of customization I don't want to lose...
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Sycobob said:
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Click to expand...
Click to collapse
Has to be simple, something like copy an update.zip onto the SD card then run the apk which will automatically run the update in the zip But my knowledge of such things is limited so I need help there
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Sycobob said:
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Click to expand...
Click to collapse
Hmm.... that sounds good.
Anybody know how to actually implement it ?
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.
The only downside to all this is that I don't know how you would flash a kernel.
Sycobob said:
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Click to expand...
Click to collapse
That makes two of us!
Sycobob said:
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.The only downside to all this is that I don't know how you would flash a kernel.
Click to expand...
Click to collapse
I'm guessing you'd just flash it as usual, surely that one is the easiest? Copying stuff to boot partition would hopefully be just as simple, I was mainly worried about updating system files. I could do with building one for the current update to test the theory!
Is there any chance we could get the icons and the clock widget of the Vertu Ti?
That is, if anyone is willing to shell out 5K on a phone just for the sole purpose of extracting .apks from it.
If you guys tell me how I can extract the apks.
BaranE said:
If you guys tell me how I can extract the apks.
Click to expand...
Click to collapse
If u have a Ti(obviously),then first i think u need to get it Rooted (sometimes stock recovery does it too)in order to extract a widget that came preinstalled,then after u root it,use root explorer to go to system/app and then look out for the widget.apk's ..
Similarly,for the icons,look for the app in system/app(using root explorer, and then copy the .apk to ur sd card,put the file on ur desktop,rename it as a zip file,extract it .
Then go to the folder called res,then drawable-hdpi and all icons will be there in .png format.
But all this is useless if u havent got it rooted,because I think u wouldn't risk to lose warranty on such a phone..
Hope this helps
Lordemort said:
If u have a Ti(obviously),then first i think u need to get it Rooted (sometimes stock recovery does it too)in order to extract a widget that came preinstalled,then after u root it,use root explorer to go to system/app and then look out for the widget.apk's ..
Similarly,for the icons,look for the app in system/app(using root explorer, and then copy the .apk to ur sd card,put the file on ur desktop,rename it as a zip file,extract it .
Then go to the folder called res,then drawable-hdpi and all icons will be there in .png format.
But all this is useless if u havent got it rooted,because I think u wouldn't risk to lose warranty on such a phone..
Hope this helps
Click to expand...
Click to collapse
It helps, though there's no root solution as of now. I don't know where to start for the root, technical support won't help. Neither will the internet. There's already a topic on XDA but no solutions.
I think you don't need root for this.
Enable USB debugging, install phone drivers to your computer, then do adb pull /system/ path-to-dump-folder.
interesting...
NeverGone\RU said:
I think you don't need root for this.
Enable USB debugging, install phone drivers to your computer, then do adb pull /system/ path-to-dump-folder.
Click to expand...
Click to collapse
I've yet to find appropriate drivers to connect to ADB. Whatever I do the phone also connects the MTP at the same time even if PTP is chosen. Any help would be much appreciated as I'd also like to backup the device via ADB. With the latest updates the phone is now running 4.2.2.
If I am not wrong, Root explorer does work on non-rooted phone.
you can access the /system partition for copying stuffs. (as you can understand without root it will only work in 'read only' mode).
Hi,
I was able to root my Ti using farmaroot just google it fairly simple method. You can also unroot to with this tool which is a plus. But I would like to know how do I access its recovery? Any help will be appreciated.
Thanks
Somebody own Vertu here?
You can extract system apps quick and easy, without root, without any risk using this tool: play.google.com/store/apps/details?id=com.ext.ui&hl=en
I'm new user, I must tolerate these idiotic rules, so I can't post links. So, please, copy this link, and open it yourself.
This gets asked quite often so I decided to make a guide on how to do this. It's a very simple process and you will need something to either freeze the .apk or something to rename it. You will also need to be rooted.
Freezing:
Titanium Backup
Rom Toolbox
Renaming:
Root Explorer
ES File Explorer
The file you will be freezing/renaming is titled SDM.apk, it is located in the system/app directory. Navigate there and freeze/rename with your app of choice. If you're going the renaming route, rename it to sdm.apk.bak, or anything else you would like as long as you change the file extension. If anyone wants a different application added to list post here or PM me and I will add it. I just listed those because they're some of the popular ones and I have used all of them myself at one time or another.
Hi, is this process make stop any apps updates and update notitfications, because except title you didn't say anything about it?
blackfire74 said:
Hi, is this process make stop any apps updates and update notitfications, because except title you didn't say anything about it?
Click to expand...
Click to collapse
No this is for the ota updates
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free