Hey guys,
I had a few questions about sideloading off market apps, that i couldn't find answers to. Thanks for your consideration.
If i understand correctly, you can only sideload apps on my unrooted samsung captivate by using a connection to a computer, right?
I know about the sideload wonder machine and i have used it successfully.
I know i could download the android sdk, and use the adb push command.
Is there a way to edit the no_market_app value in the settings db file only using my un-rooted phone?
Or can i use terminal emulator or a combination of both to somehow install an off market app?
I was just trying to think of ways to avoid having to conncect to a computer to install an app. I was on the road with a friend, and i had an off market app i wanted to give him, but he also has att(which blocks sideloading of off market apps), so i didn't even try. But wouldn't it be awesome if i could send the apps to his phone through bluetooth or email, then install it on his phone without rooting his phone? Maybe a temporary root of some sort would work? Isn't that how swc works?
Anyways, once i've played enough with my stock phone, i'll beg for more and i'll eventually root, and i'll probably end up playing with the sdk too. Thanks again guys!
To Root or Not To Root... or Perhaps Just A Temp Root...
There are a few quick fix temp root apps floating around. It really depends on you model and build if they work correctly or not.
You could, as you mentioned, push from a cmd promt in adb, install from the cmd promt in adb to the device - or - pull from the device itself using a shell or terminal.
Unfortunately, I currently don't know of a direct way that you would be able to access, let alone edit the system.db file to make a permanent modification without at least being under a temp root.
Peace-
I have already rooted my Droid 3( the system is Verizon 906) , but when I use adb to contol it, I cannot get it run on root directly. I need to exploit it and reboot my phone to make adb run on root.
How to make adb run on root directly?
lzy0702 said:
I have already rooted my Droid 3( the system is Verizon 906) , but when I use adb to contol it, I cannot get it run on root directly. I need to exploit it and reboot my phone to make adb run on root.
How to make adb run on root directly?
Click to expand...
Click to collapse
So do you want any ADB command you send to the phone to have root privilege?
If you run ADB SHELL and then run su in the shell, you will get root privilege for that session (is that not enough for what you're trying to do?)
LaZiODROID said:
So do you want any ADB command you send to the phone to have root privilege?
If you run ADB SHELL and then run su in the shell, you will get root privilege for that session (is that not enough for what you're trying to do?)
Click to expand...
Click to collapse
It does work! Thanks a lot.
I had Emanon's ROM on it for a while, but it just came crashing down so I flashed CM7.2... boots a lot faster, seems a bit more stable.
But I used to have full access, and now I don't. How do I get it back? I just want to switch out the bootanimation.zip.
Came across this:
status_six said:
Hi there, you need to have s-off (aka security off or full root) to write to /system and /data with the device booted, i.e. using root explorer etc.
You can also do it with s-on, but you have to to that with your PC via cmd prompt and adb shell which is less convenient.
Great guide to getting s-off here, took me <10 mins!
http://forum.xda-developers.com/showthread.php?t=794314
Click to expand...
Click to collapse
I've just finished mucking around with a HTC, so I'm a bit confused, but I gather there's no fastboot mode on the Mini, so I can't see how I can access the phone's flash from the PC without using the ADB shell...
And I'm not sure s-on/off is even relevant to the Mini... halp!
Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?
Kimmoth said:
Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?
Click to expand...
Click to collapse
Go to the su app and grant the permission for ES
you are coming from HTC so I am clearing some points some of them are of-topic
no fastboot instead download mode
bootloaders are not locked so no s-on no s-off in Samsung devices
use Odin multidownloader to flash firmware through PC
never use rom manager on this mobile, else a brick will be waiting for you
galaxy mini is easily root able
just flash an update.zip in recovery and you will be rooted
after root to change something in system
type mount -o remount,rw /system then do whatever you want to
stock rom cannot be backed up with the help of cwm
Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.
Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.
doublea70 said:
Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.
Click to expand...
Click to collapse
Yes. The un-updated version of Su should be enough to give ADB root, so you can use ADB to remount the filesystem with r/w, then push the new su.
For future readers who don't know:
First, navigate to ADB in the terminal of your choice (Command Prompt on Windows, Terminal on Linux/OS X. I'll be using Windows.)
Do this by typing
Code:
cd /your directory ADB is in/
In my case, it now says "C:/Users/MyName/Desktop/ADB" because I keep ADB on my desktop like a silly person.
Now, remount your filesystem in ADB with read/write access. The command is
Code:
adb shell su mount /system rw
Now, we can push that new SU binary with ease, with
Code:
adb push c:/The_Directory_you_keep_su_in/ /system/bin
In my case, It was just "adb push c:/su /system/bin" because I keep files I want to push on the root of my hard drive, like a silly person.
Now, switch system back to read only with
Code:
adb shell su mount /system ro
All done, use Superuser app to Check for updates. It should say you're up to date, and if you update anyway, it'll do it without failing.
Is there another method to this? I have this problem idk why it says I have root saved but it won't let me restore? I don't have computer access and my root keeper says I have root?
Sent from my MB886 using Tapatalk 2
Gaining root access... fail!
ripin150 said:
Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.
Click to expand...
Click to collapse
After following all the steps. When i install root checker, it is telling me i don't have root.
Below is what i got back from superuser:
Su Binary Updater
Downloading Manifest... Okay!
Parsing manifest.. Okay!
Latest version = 3.1.1
Checking installed version = 3.1.1
Upacking sutools... okay!
Checking current install path.. /system/bin/su
Downloding new binary.. okay!
Gaining root access... fail!
Any idea to help?
i have installed android studio and using Android 7.0 API 24 android virtual device.. i wanted to install xposed on it but for that i need root access...
i tried to start virtual device from emulator command line by using -writable-system .. after i used root and remount command through adb and pushed su to /system/bin/su and give permissions to it
after i installed supersu apk and rooted device succesfully.. but issue is when i reboot virtual device it go into bootloop.. if i do cold boot from android studio it again loose root access..
kindly suggest what i do.. i read somewhere to copy system.img from temp folder but i am not able to find system.img in any temp folder
PS::I AM USING WINDOWS 7
saahil40 said:
i have installed android studio and using Android 7.0 API 24 android virtual device.. i wanted to install xposed on it but for that i need root access...
i tried to start virtual device from emulator command line by using -writable-system .. after i used root and remount command through adb and pushed su to /system/bin/su and give permissions to it
after i installed supersu apk and rooted device succesfully.. but issue is when i reboot virtual device it go into bootloop.. if i do cold boot from android studio it again loose root access..
kindly suggest what i do.. i read somewhere to copy system.img from temp folder but i am not able to find system.img in any temp folder
PS::I AM USING WINDOWS 7
Click to expand...
Click to collapse
I suggest you to use Instapaper. Because it offers a Kindle app for Amazon's eReaders that let you read text-based versions of your saved articles. These text-only versions are designed to be easily read on eInk displays. You can shift the articles via USB, or set up wireless delivery via a newsletter that can be automatically downloaded to your Kindle as often as once per day. Once downloaded, the articles are accessible even when you're away from wifi.