Related
Hi all:
I have read and searched and tried and tried and FAILED. I can not enable sideloading on my Captivate after the JH7 update.
Is there any such thing as a "One Click Sideload Enabler".
Now, I don't mean something like the Wonder Machine, or Droid Explorer (which I am currently using to install apps). I mean a way to easily enable sideloading on the actual phone itself.
Before the update I used Unleash the Beast, which worked perfectly. Sadly it will not work after the update, and the developer seems to be gone
Any thoughts?
Thanks!!!
You need to root and then modify settings.db to allow side loading. I know of no other way. This is how i have done it in the past.
Hi:
That is the first thing I tried. I have tried to edit with sql lite, as well as root explorer, it shows the value of non-market apps changing to 1, then I transfer it back to phone, but I am still unable to install non-market apps.
I think a main part of the problem is that when I try to copy the settings.db file to desktop through cmd prompt, it does not copy. I actually had to use root explorer to copy it, then transfered it to PC, then made the changes.
I was actually hoping for something similar to what Unleash the Beast did. After you installed UTB, you could then just use Terminal editor to very easily enable sideloading. I believe UTB has a script of some sort which made that possible.
Thanks!
+1 for a non-market app / sideloading "update.zip" (JH7 compatible of course).
The problem with an update.zip format fix is that we'd essentially have to overwrite your settings.db, and you would lose any customization off of stock not already made.
Perhaps an update.zip that contained sqlite3 and a shell script ?
Hi:
Thanks so much to everyone who replied. After trying a million times, I was finally able to get sideloading enabled. It seems that my JH7 update hadn't properly flashed. After reinstalling the update things went smoothly.
Thanks again!
Glad to hear it.
Hey all -- so i flashed back to JH6 with ODIN, got the JH7 update through Kies Mini, and then rooted. I also decided to use Launcher Pro as my default homescreen launcher.
Now i'm trying to use SWM to sideload some apps, but I always get the error (something like this) FAILED INSTALL PARSE UNKNOWN EXCEPTION ... the program recognizes my device just fine and loads up the .apk just fine but fails on trying to install it onto my phone.
anyone have an idea of what might be going on
SWM is unnecessary after root isn't it
Sent from my SAMSUNG-SGH-I897 using XDA App
Tchem said:
SWM is unnecessary after root isn't it
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2 are not related. You do NOT need to root to use Sideload. The SWM just uses the ADB command from the SDK. You can do this all day long without root.
If you want to install apps from your phone (not your PC) then you need to root and then you need to edit the settings.db file to allow sideload on the phone. You can't get to settings.db without rooting your phone.
Does that help?
alphadog00 said:
The 2 are not related. You do NOT need to root to use Sideload. The SWM just uses the ADB command from the SDK. You can do this all day long without root.
If you want to install apps from your phone (not your PC) then you need to root and then you need to edit the settings.db file to allow sideload on the phone. You can't get to settings.db without rooting your phone.
Does that help?
Click to expand...
Click to collapse
sort of not really, as i'm trying to upload apps/widgets from my pc. i want to hold off buying Root Explorer, and apparently Droid Explorer doesnt work on win7 64-bit systems yet ... just kind of odd that SWM can't load to my phone. i either get the INSTALL PARSE FAILURE UNKNOWN EXCEPTION or INSUFFICIENT SPACE or OLDER SDK errors. doesn't make sense to me...
turn debugging on ,
don't put the .apk files in the sideloader folder at all. caused the whole no space avaliable for me when i did that
try that... works for me.
updated with the ota an i'm rooted.
yeah i had debugging on, left the apks in a completely separate folder (didnt put them in the payload folder). the main failure i get is the install parse unknown exception one
im thinking it might actually be the apks i'm trying to upload. i got one apk to upload successfully, so maybe the other ones have some bad code in them. *shrug*
specifically i've been trying to upload the REVOlution transparent apps. all of them fail for me. then i uploaded minimal icons apk just fine.
Would appreciate it if someone can explain to me the difference between a kernel and a Rom.
And also, what does it mean by "pushing to /system/app"?
Thanks in advance.
http://lmgtfy.com/?q=kernel+rom
Can someone guide me on how to push an app to system/app please?
I know it has something to do with ADB but I do not know the exact steps. Thanks.
At first you need root access. Then you need an app like 'Root Explorer' and with this app you can push files into /system - folder.
Sent from my GT-I9000 using XDA Premium App
Imagine a rom as a car. The kernel would be the engine.
Sent from my DynaTAC 8000X
sendokan said:
http://lmgtfy.com/?q=kernel+rom
Click to expand...
Click to collapse
How about a better answer?
A kernel is a piece of software (kind of like a program/executable) that interfaces directly with your hardware and provides a standardized interface for higher level software to use that hardware.
ROM means Read Only Memory. In this case, ROM is not the proper term but it is in common usage despite the fact that you can write it/overwrite it. Regardless of the details, for your purposes, a ROM is the higher level software that provides interfaces between the kernel and you. E.G. the libraries, windows manager, etc.
I am unsure in this context, but I think the ROM contains the CSC stuff too. The CSC contains stuff specific to a particular locale or vendor such as programs like Layar or codes for APNs.
I followed the above Let Me Google That For You link and this thread was the first one that popped up. I quickly browsed a few other threads but getting any real meaning was going to be quite tedious.
Good luck and have fun.
strikethree said:
How about a better answer?
A kernel is a piece of software (kind of like a program/executable) that interfaces directly with your hardware and provides a standardized interface for higher level software to use that hardware.
ROM means Read Only Memory. In this case, ROM is not the proper term but it is in common usage despite the fact that you can write it/overwrite it. Regardless of the details, for your purposes, a ROM is the higher level software that provides interfaces between the kernel and you. E.G. the libraries, windows manager, etc.
I am unsure in this context, but I think the ROM contains the CSC stuff too. The CSC contains stuff specific to a particular locale or vendor such as programs like Layar or codes for APNs.
I followed the above Let Me Google That For You link and this thread was the first one that popped up. I quickly browsed a few other threads but getting any real meaning was going to be quite tedious.
Good luck and have fun.
Click to expand...
Click to collapse
first one is a thread from a year ago with exactly the same title
The kernel manages system resources and functions like a bridge between applications and hardware. One could compare it in many ways, but this is generally what it does.
Thanks all for the explanation. Will search around to understand the differences.
Lunchbox115 said:
At first you need root access. Then you need an app like 'Root Explorer' and with this app you can push files into /system - folder.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
May I know how exactly do I push the apk to /system/app? I have Root Explorer installed already.
Do I move the apk to /system/app then install it from there? Or am I supposed to install the normal way, then shift the apk from /data/app (where apps are usually installed to right?) to /system/app?
Which *.apk do you want to install?
Normally you just have to click on the *.apk (with any file manager) and you can install it.
At first, you need root.
After that, you have a few ways to do this:
Way 1: Use any File Explorer, which can get SU permission and access the system folder.
Then copy & paste
Way 2: You could connect your device to your computer with a USB cable (Debug-Mode on!).
Then you couls google a ADB tool.
Or you open the command line and type this into your cmd:
cd [drive]:\[folder where adb is located]\
adb root
After that you could find out where you are with the "ls" command.
Sent from my GT-I9000 using XDA Premium App
Lunchbox115 said:
Which *.apk do you want to install?
Normally you just have to click on the *.apk (with any file manager) and you can install it.
Click to expand...
Click to collapse
I am actually trying to do this --> http://forum.xda-developers.com/showthread.php?t=1123830
Installing
You can install the EDT Tweaks app or you can push it to /system/app
You must push SystemUI.apk to /system/app
I don't want to make a flashable quite yet because I want more experienced users to test this out, etc
Click to expand...
Click to collapse
So am I supposed to push first then install or the other way round?
I tried installing the normal way, then shifted the apk from /data/app to /system/app but received an error when I tried to open the app.
Anybody please?
EDIT: Fixed! Procedure I used was to download Danifunker's system dump, move it to /sdcard/ via adb push, then run the following:
Code:
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
This completely refreshed my /system folder. Original post below:
--------------------------------------------------------------
Hello XDA forumgoers, longtime reader first time poster here. I'm currently posting because I made a few mistakes. Several mistakes, actually.
1. In my quest to de-bloat my XT860, I accidentally removed one file too many, which caused my phone to mysteriously not have a cell signal. (com.motorola.service.main kept crashing.) So I hit the forum and grabbed a system dump from this thread (thanks Willis111):
http://forum.xda-developers.com/showthread.php?p=17501981
I had bought the phone with some version of Cyanogenmod Recovery installed by the previous owner, so I was able to use that and ADB to stick the .apks and .odex files in the /system/app folder, chmod 644 them, and even factory reset for good measure.
2. As I soon found out, I had somehow made things worse. The phone, when boot into, shows the "press android to begin" page, but com.motorola.service.main and some other apps keep FCing on me, and I can't progress past that screen. In my haste, I didn't backup any of my system folders at all, though, I still backed up my apps with Titanium.
Tl;dr:
presumably none of the /system/app apks boot, most notably com.motorola.service.main. How do I fix this? Can I?
Try to flash
http://forum.xda-developers.com/showthread.php?t=1288823
You also need to chown 0:0 both the apk and the odex
Have you tried using my original system dump? It was taken with dd, so things like symlinks and the other sort should be functional. The only caveat is that a number of apps were frozen at the time, so you may need to unfreeze them with titaniumbackup.
http://www.multiupload.com/SORQERFAYT
DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?
jonsicoli said:
DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?
Click to expand...
Click to collapse
What about rootkeeper?
DoubleYouPee said:
What about rootkeeper?
Click to expand...
Click to collapse
I can't get past the "click android" screen, so I probably can't install or run it. Any way to do it via adb or Cyanogenmod Recovery?
I really appreciate the help.
jonsicoli, if you want to restore your *entire* /system folder (not just apps) you would run a similar command-set as this.
1. Copy the file to the internal memory
adb push c:\path.to.folder\mmcblk1p21.img /sdcard
the file will be located in the root of the sdcard (or you could drag and drop the file in USB storage mode)
2. Do a full restore on system memory *I have not checked to ensure this is working... but a command similar to this should work
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
- wait -
(it would have to write about 500mb and replace all of the contents of /system )
reboot
_______________________________________________________
Okay, if you just want to look at the files, you could use a linux machine to mount the filesystem (it is a standard ext3 FS) or you could do what I have done on my windows system:
Install EXT2FsD from http://sourceforge.net/projects/ext2fsd/files/latest/download?source=files
Then install OSFMount from http://www.osforensics.com/tools.html
Point the OSFMount program to the img file that you downloaded and assign it a drive then voilla!
I am pretty sure this is a bit of overkill, but this should completely restore your system close to factory (minus the APKs that were upgraded/disabled, plus the fact root was done)
Thanks Danifunker! I reset my entire /system folder, and restoring my user app backup. I'm just relieved to have my phone back. Now to mark this thread as solved.
Awesome!!!!!! Glad to hear my system dump works! Thanks for testing
My command lines were written correctly also I guess?
Sent from my XT860 using XDA App
searched for like 8 hours until i found this thread. Just what i needed, i had system image for 2.3.6 from your other post but no command.
Hi All,
Since I am getting nowhere and no replies for my questions, I am going to rephrase them differently here so hopefully someone can jump in and give me a helping hand... (and please forgive if I seem to bombard the forums with questions).
My Note 3 SM-N900A, build KOT49H.N900AUCUCNC2, running 4.4.2. It is having issues with permissions that effectively block the phone from seeing any SD Card, USB, and internal memory space. It won't access any remote resources like internet or Google Play...either
Issues arose after I changed platform.xml. I since then unrooted the phone and uninstalled SuperSU. I can see that these 3 changes were reckless on my part, that I just put the phone into a very bad state that made it very very difficult to recover. I am still banging my head for the blunders but obviously that didn't help fix the phone. :crying:
I would like to know if there is a way to gain access to the phone's system area again to fix the permission issues. Can I use ADB Shell along with USB debugging? If yes, what are the commands I need? Can I somehow send towelroot and SuperSU to the phone via Odin and execute them? The reason I ask this is that I have no way to access any storage area on the phone, and there is no way to go online to download apps. Or can I put the phone into service mode by typing in the *# numbers on the keypad and hopefully fix it there?
Thank you
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
OK, Something Positive
andygev35 said:
At this point I'm not even sure if adb would be able to access your memory card to push TowelRoot to it. You might be best off restoring using the stock Odin files, lick your wounds, start over and chalk it up as a learning experience.
http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
vbcomer said:
Ah, thanks for replying. I was really worrying about that too.
However, I just installed ADT on my PC and connected to the phone via USB debugging. Using the adb shell ls command, I could see the entire directory structure. I was able to get to the system folder too.
I pulled the platform.xml back and attached to this message. Could you or someone please take a look and let me know if anything is wrong in the file? I made very small changes and reverted them. So it should be same as original, but I am not so sure. Also do you know if the encoding of the file is wrong so that Android couldn't read it?
At this point, it appears all is NOT lost. I just need some of your experts to guide me thru the commands needed to regain the access to my SD card or storage from the phone.
Now, let me bring in another point: Prior to having all this snafu, I granted ES File Explorer root access so that I could overwrite the platform.xml file. I don't know if doing that messed up the system. If it did, what would be the most straight forward way, simplest way to try to get back to normal? Provided now adb seems to be able to access the files and directory.
I know I could try install towelroot again, but would like to see if I can bring the system back to normal operation first.
Thanks
Click to expand...
Click to collapse
Here's the original stock platform.xml if it helps you.
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Edit: instead of using adb push, use "adb install towelroot.apk" (if that's the actual package name). Go through the rooting process, download the ES File Explorer apk to your computer install it using adb. Hopefully if all that works, you'll be able to check and fix any permissions that got messed up with your platform.xml. It should be rw-r-r.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
A Step Forward
andygev35 said:
I may be wrong, but adb being able to see and pull system files is one thing. To get adb to actually modify system files, you'd need to be able to give adb root access. You may however be able to download the TowelRoot apk to your computer, put it in the same directory as adb, then in the command prompt type "adb push towelroot.apk /data/app/" (without quotes). Reboot and see if TowelRoot installed.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Update: I saw the Towelroot app in the App Drawer, but after clicking on it and choosing "make it ralr", I got message "Unfortunately, towelroot has stopped."
vbcomer said:
OK. You are right. adb doesn't have write access yet.
I tried this and got success:
C:\AndroidDev\sdk\platform-tools>adb install tr.apk
1767 KB/s (113099 bytes in 0.062s)
pkg: /data/local/tmp/tr.apk
Success
What should I do next? Does it mean the tr.apk has been installed?
Thanks
Click to expand...
Click to collapse
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
Sounds as though towelroot is now installed. Go to your app drawer and run it.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
vbcomer said:
Yeah, it is installed in the App drawer, but running it gave me error "Unfortunately, towelroot has stopped.".
I went ahead and install both ES File Explorer and SuperUser packages. From ES FE, I could look at the /system/ect/permissions/platform.xml and could see that it had a different date, its date is older, 3/15/2014. I think it came with the N900AUCUCNC2 that I flashed with Odin yesterday.
So, it appears the permission come from a different place or source, I would like to know where Android actually sees the permissions. You know, how did it think that it needed to lock down read/write access to storage areas while the /system folder has been replaced.
Thanks
Click to expand...
Click to collapse
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
andygev35 said:
I'm at the limit of my experience here... Did you do the all in one restore or the 4 file restore?
Sent from my AT&T Galaxy Note 3 using Tapatalk®
Click to expand...
Click to collapse
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
vbcomer said:
Thanks for hanging in and helping, you don't know how much I appreciate your time!
I did the all in one first. That didn't help. Then I did it again with the re-partition with PIT file. But that didn't help either. I didn't try the 4 files individually for fear of losing data.
Click to expand...
Click to collapse
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
brisinger08 said:
I think you've just about done everything you can do without a complete Odin reinstall and reformat. If adb pull is working for you I suggest pulling the folders you want to save and doing the complete 4 file install with the PIT file as well.
Someone more experienced than I may be able to get you back up without losing your but tbh with the amount of troubleshooting you've done already I think a full Odin reinstall is your best option and will prevent any issues that could stem from this further down the line.
The only thing I can think of with towelroot is that it needs internet access to run were you connected to wifi when you ran it? It's probably not that simple but figured it couldn't hurt to try!
Click to expand...
Click to collapse
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
vbcomer said:
Hi there,
Thanks for replying. I am kind of afraid I will have to go down that route, but at the same time trying not to if I could.
One of the other reasons I didn't try the 4 files was because I thought the all-in-one, as its name suggested, would be equivalent to those 4 files.
Is there a way to pull the SMS, MMS, call logs from the phone via adb? Do you know where those records are kept?
Thanks
Click to expand...
Click to collapse
The all-in-one file is the same as the 4 files, the only difference is installing it doesn't wipe the internal storage.
Have you tried running adb backup? That would be a heck of a lot easier than pulling a bunch of folders...if that doesn't work the databases are in /data/data
Calls: /data/data/com.android.providers.contacts
SMS and MMS: data/data/com.android.providers.telephony
Is there is any shell command to long tap