I'm on Bugless Beast Jellybean (8-7 build) running Franco's kernel. None of my kernel settings, minfree settings, or VM cache settings will "stick" after a boot. I noticed I did not have a /etc/init.d folder or a syscntl.cfg file anywhere on my system. I tried manually adding these files, adding scripts, and totally opening permissions (0777) on the folders and files, then rebooting into recovery, wiping cache/dalvik, and rebooting. Nothing still sticks. Is there a way to get this to work without unpacking / repacking my boot image, preferably a way to add the init.d folder (manual or flash a .zip), or secondly using some sort of auto-script tool? I have my build.prop set up how I want, and that sticks. Thanks for any suggestions, and sorry if this has been answered elsewhere - I'm a noob to the site, but I did search first!
You should install supersu from the market, open it and it will update binary and be the default su application. All settings will stick than
Sent from my Galaxy Nexus using Tapatalk 2
Different than Superuser?
dascjb said:
You should install supersu from the market, open it and it will update binary and be the default su application. All settings will stick than
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You're thinking of a different app than the Superuser (by chainsdd) app? If so, I'll give it a shot. Thanks!
Yeah, supersu by chain fire.
Sent from my Galaxy Nexus using Tapatalk 2
Trying it out!
dascjb said:
Yeah, supersu by chain fire.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll give it a shot. Thanks again.
Partial Fix
dascjb said:
Yeah, supersu by chain fire.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So, supersu fixed one of my issues - the Franco kernel settings now stick (thanks!). However, I still can't get minfree settings to stick after a boot. It seems that any scripts I write in /etc/init.d/* are not being read. Suggestions on how to get minfree and VM cache settings to stick?
pkgnex said:
So, supersu fixed one of my issues - the Franco kernel settings now stick (thanks!). However, I still can't get minfree settings to stick after a boot. It seems that any scripts I write in /etc/init.d/* are not being read. Suggestions on how to get minfree and VM cache settings to stick?
Click to expand...
Click to collapse
Do you have busybox installed?
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
Also did you add sysctl.conf in system? and not syscntl.cfg?
sysctl
dascjb said:
Do you have busybox installed?
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
Also did you add sysctl.conf in system? and not syscntl.cfg?
Click to expand...
Click to collapse
I do have the latest busybox installed.
As of right now, I actually am re-trying one step at a time... at the moment I have no sysctl.conf, trying to get /etc/init.d/tweaks file to work, still no luck.
Not sure if it is required but all files in my init.d all started with a number ie. 98tweaks
Sent from my Galaxy Nexus using Tapatalk 2
Yeah
dascjb said:
Not sure if it is required but all files in my init.d all started with a number ie. 98tweaks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I've actually been doing that just in case!
Did your rom come with an init.d folder, or did you flash something to get it or create it "by hand" like I'm trying to do?
pkgnex said:
Yeah, I've actually been doing that just in case!
Did your rom come with an init.d folder, or did you flash something to get it or create it "by hand" like I'm trying to do?
Click to expand...
Click to collapse
The ROM I am using now came with the init.d support. Not sure if it matters but it looks like there is a symlink from /etc to /system/etc
symlink?
dascjb said:
The ROM I am using now came with the init.d support. Not sure if it matters but it looks like there is a symlink from /etc to /system/etc
Click to expand...
Click to collapse
Which means? How do I handle this?
pkgnex said:
Which means? How do I handle this?
Click to expand...
Click to collapse
you would need to use terminal emulator app or, easier, adb. If you connect your phone and type in 'adb shell' you will get a terminal on phone. You should be able to just type
su
ln -s /system/etc etc
this will make the symbolic link from the root of the device to /system/etc
alternate method
pkgnex said:
Which means? How do I handle this?
Click to expand...
Click to collapse
Looking into work-around's, found "smanager" app to run scripts. It successfully executed my minfree script, so if the "set at boot" option works, it will be what I need (albeit through and app and not purely at the system level). It's progress!
dascjb said:
you would need to use terminal emulator app or, easier, adb. If you connect your phone and type in 'adb shell' you will get a terminal on phone. You should be able to just type
su
ln -s /system/etc etc
this will make the symbolic link from the root of the device to /system/etc
Click to expand...
Click to collapse
Just symlinking /system/etc to /etc won't magically make init.d scripts work if the init.d service isn't being invoked in init.rc.
You need a ROM/kernel that will support init.d scripts. If the ROM/kernel don't support init.d, then you can't get them to auto-run on boot, except for work-arounds like using Script Manager to run them on boot.
Also, your link command is only correct if you're in the root directory of your phone. Executed from anywhere else, you don't end up with /etc. It should be:
ln -s /system/etc /etc
Related
I've noticed that the su binary installed by superuser doesn't survive a reboot. Anyone else have this problem? Any fixes?
Sent from my SPH-D700 using XDA App
Same here. Have to re update after each reboot
Sent from my SPH-D700 using Tapatalk
same here, had to update the binary too
How do you update the su?
Launch superuser, go to settings and scroll to the bottom.
Sent from my SPH-D700 using XDA App
I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App
dangdang said:
I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
How did you update it yourself?
Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App
Code:
#cp /sdx/su /system/bin/jk-su
cp: not found
the last part does not work (i have the same root method)
i have to re-root the phone when i get home today. but i will try to move the updated binary with root explorer instead of the command line.
Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA
dangdang said:
Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA
Click to expand...
Click to collapse
will try I had the same issues
dangdang said:
Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have this exact same problem on my Samsung Moment (have to update SU every reboot).
The directory structure seem a bit different. For example, there's no /system/bin/jk-su (in fact, if I find / -name 'jk-su' I get no results at all).
I am poking around the directory structure trying to figure out where to find the source and destination su files that I'm going to have to overwrite and I can't seem to figure which is which. Does anyone have any idea how to do the functional equivalent of dangdang's post on a Moment?
Thanks!
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao
I was about to say. WTF is everyone talking about SU not surviving a reboot /noodlescratcher
davidrules7778 said:
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao
Click to expand...
Click to collapse
k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
lol. i hear ya!
DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse
DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse
most likely SU is built into your kernel and short of rebuilding or repacking your kernel you cant update it..
I have a samsung galaxy s I9000 running Gingerbread will this work for me..?
I am using the rom IML74K Android 4.0.3 Build 8 from bigxie and franco.Kernel #13.
I think the rom and kernel suppose to support init.d scripts. And I can found the script in etc/init.d named 97schedmc.
I wanna the hotplug function, so I put a file named 98hotplug(I don't know how to named the script), but I found it would not work. The parameter would not change after restart the device. Even I excute it(rename to sh file) in RootExplor, the parameter did not changed.
I try to run or sh the command in adb shell, it works fine, and the parameter changed.
I thinks it is relate to the access right issue, but I don't know how to fix it.
Could any one can help me?
Thanks for the guy who reply me.
you most chmod the files. Just sticking them it won't allow them to run.
I am not such understand... What should I do then?
chmod them?
755 works.
Hi,
Like this:
For 755,right permissions for scripts in Init.d folder,a good link i think: http://www.elated.com/articles/understanding-permissions/
Do not create a sh. file,for example in Root Eplorer,go to system/etc/init.d and menu/New file then put your script with #!/system/bin/sh first then space then enter.
Or on your pc take a init.d file in a rom,erase the script,copy yours with the correct script,reput in your phone,set the correct permissions then reboot.
Are you really sure your rom/kernel suppot Init.d ?
Just one question,I do not use this combo...
Hoping this helps
Permissions are set correctly, the kernel (faux123) supports init.d scripts, and the script works when run from terminal, but it still does not run on boot.
Thanks for your reply and great help!
I am sure the kernel support the init.d, but I not sure the rom, is it necessary both of them to support init.d?
What is your combo??
Hi,
To monkeyzou,yes i use the same kernel wich support Init.d script,but i use aokp rom,the rom you are using seems not support Init.d (it is not specified?),but in any case the Franco kernel support it,and it create the necessary lines in "init.rc" for activate the init.d support+the init.d file+the correct permissions,all automatically when you flash the kernel...
So i don't now what is wrong
Are you sure you set the right permissions for your file script in init.d?Are you sure your script is written correctly?
Can you share it?
After that my knowledges stop there,sorry...
init.d support only needs to be in the kernel ramdisk. As for rom support, that only goes as far as needing the directory. Note that some of the kernels out there are anykernel format and therefore would not support init.d scripts.
I was trying to do the exact same thing and couldn't make it work either. Eventually I just used Script Manager (on market) and let it run the script at boot.
Here is my script:
Code:
#!/system/xbin/bash
echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
Re,
To monkeyzou can you test this script at the bottom of my message?
Remove the .txt and copy it to your init.d folder then set the right permissions for it as i have shown above.
Or test another script where you could see a change?
At the end are you sure your script don't work?
After reboot with the script go to /sys/module/dsscomp/parameters/hotplug_enabled and see if the value is set to 1,if yes it's ok,if no (so set to 0),i don't know more...
ctbear said:
I was trying to do the exact same thing and couldn't make it work either. Eventually I just used Script Manager (on market) and let it run the script at boot.
Here is my script:
Code:
#!/system/xbin/bash
echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
Click to expand...
Click to collapse
Hi,
Test the script i've posted above:
#!/system/bin/sh
echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
Click to expand...
Click to collapse
I hope that helps
viking37 said:
Hi,
Test the script i've posted above:
I hope that helps
Click to expand...
Click to collapse
Thanks. Unfortunately it still didn't work, but I've found a workaround (looks stupid, but somehow works):
Basically I have a script file at the root of storage, and it contains just the echo line. My init script will just run that /sdcard script and it works fine.
viking37 said:
Re,
To monkeyzou can you test this script at the bottom of my message?
Remove the .txt and copy it to your init.d folder then set the right permissions for it as i have shown above.
Or test another script where you could see a change?
At the end are you sure your script don't work?
After reboot with the script go to /sys/module/dsscomp/parameters/hotplug_enabled and see if the value is set to 1,if yes it's ok,if no (so set to 0),i don't know more...
Click to expand...
Click to collapse
Tried this script and it works
I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.
adb remount
adb push filename /system/xbin
Sent from my HTC One X
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590
realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.
Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.
Hey Everyone,
Trying to modify /sys/module/msm_otg/parameters/usbhost_charge_mode from it's default value of 'Y' to '1' in order to enable usb charging + OTG while using ElementalX's kernel. No matter what I do, I get either access is denied, or when trying to commit a change with sysctl I get nothing as the changes aren't being saved. Been working on this for the past 6 hours and can't figure it out!!! I know there's an easy straight forward way to do this, just can't figure it out!
Please help!!
Thanks,
Noob
Youve mounted R/W right? Or should I say write? Ahah software puns.
Sent from my Nexus 7 using XDA Free mobile app
Mounted as r/w and rooted...
THEBANDIT420 said:
Youve mounted R/W right? Or should I say write? Ahah software puns.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, meant to add that detail last night but forgot in my frustration. Mounted as R/W, also, did a chmod 777 on the file as well to verify perms were correct.
Tried doing all this work via terminal vi which didn't work, then tried doing an adb pull, update the file adb push, which resulted in a permissions failure. Everything leads me to believe that my root isn't a FULL root; however, I can't find another method of performing said root. Used WugFresh Nexus Root Toolkit v1.8.3 to perform root.
Thanks for your help man,
Noob
Anyone?
Can anyone help? This is driving me absolutely insane!
n00b5auc3 said:
Can anyone help? This is driving me absolutely insane!
Click to expand...
Click to collapse
Try to do that with Root Explorer
Here's what I've done so far
matcho13579 said:
Try to do that with Root Explorer
Click to expand...
Click to collapse
Just tried what you suggested, it appeared to save; however, upon verification, the file reverted from '1' back to 'Y'.
So far I've tried:
Using a chmod 777 on the file via su terminal, edit file with vi, attempt to save - result - failure..
Using ES File Explorer with root permissions and mount /system in RW enabled, nav to file and edit with ES text editor, save - result - failure...
Mount /system as RW using some app I can't remember, then navigate using ES File Explorer to location, edit using ES text editor, save - result - failure...
adb pull on the file, update, adb push back to location - result - failure
su attempt to delete, move, and rename file in an effort to replace it - result - failure....
I'm pretty sure whoever made that file had ninja training, because every time I try to touch it it totally evades me. -_- Anyways, thanks for the help in advance.
n00b
Anyone? Bueller.... Bueller?
Someone has to have ran into this problem before....
Saw this posted on Reddit. Seems to be a full system image but I'm not brave enough to flash it
https://mobile.twitter.com/MotoFirmware/status/522902016763633665?s=09
Slack3r said:
Saw this posted on Reddit. Seems to be a full system image but I'm not brave enough to flash it
https://mobile.twitter.com/MotoFirmware/status/522902016763633665?s=09
Click to expand...
Click to collapse
I think no problem.You can try it.
You can mount it as loop and explore it, I suppose.
Sent from my GT-N7100 using XDA Free mobile app
There are some wifi config files and binaries, the factory test packages, etc..
I found this app, that can be installed in the current system with adb: (motoCompass.apk)
https://drive.google.com/file/d/0BxTLcy78OveNRjZkYzJaRmJ4S0U/view?usp=sharing
More goodies:
Moto 360 gears boot animation: http://youtu.be/Rje-O0P6PJo
Sent from my GT-N7100 using XDA Free mobile app
Here's a dump of the system partition, lots of interesting things!
https://drive.google.com/file/d/0BxTLcy78OveNSmJrdTM2SkxEYVE/view?usp=sharing
Enjoy and share your findings
dproldan said:
There are some wifi config files and binaries, the factory test packages, etc..
I found this app, that can be installed in the current system with adb: (motoCompass.apk)
https://drive.google.com/file/d/0BxTLcy78OveNRjZkYzJaRmJ4S0U/view?usp=sharing
Click to expand...
Click to collapse
I installed the compass app, it's hardly what I would call accurate but it does seem to get the right direction for the most part. Good find!
dproldan said:
More goodies:
Moto 360 gears boot animation: http://youtu.be/Rje-O0P6PJo
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe I'm missing something trying to get the gears animation in my watch. I set up Bluetooth debugging and then tried
adb -e push bootanimation.zip /data/local
I'm a little rusty on adb commands and would appreciate any assistance. Thanks!
neilrl79 said:
Maybe I'm missing something trying to get the gears animation in my watch. I set up Bluetooth debugging and then tried
adb -e push bootanimation.zip /data/local
I'm a little rusty on adb commands and would appreciate any assistance. Thanks!
Click to expand...
Click to collapse
You may need to just give it some time, it took a good 10 minutes or so for it to finish anything for me over bluetooth. It just sat at the prompt without giving me status information or anything.
dproldan said:
There are some wifi config files and binaries, the factory test packages, etc..
I found this app, that can be installed in the current system with adb: (motoCompass.apk)
https://drive.google.com/file/d/0BxTLcy78OveNRjZkYzJaRmJ4S0U/view?usp=sharing
Click to expand...
Click to collapse
WiFi config files for the watch? Interesting..!
neilrl79 said:
Maybe I'm missing something trying to get the gears animation in my watch. I set up Bluetooth debugging and then tried
adb -e push bootanimation.zip /data/local
I'm a little rusty on adb commands and would appreciate any assistance. Thanks!
Click to expand...
Click to collapse
abd won't let you put anything in /data or /system, as it's not running in root mode.
You have to push it to /storage/sdcard0/ then enter an adb shell, get root with su, remount /system and copy the zip from /storage/sdcard0/ to /system/media/
So what can we do with this
Anyone wanna mirror this? It seems they took it down...
r3pwn said:
Anyone wanna mirror this? It seems they took it down...
Click to expand...
Click to collapse
Found it
Here
https://www.androidfilehost.com/?fid=95916177934554712