Thanks go to goroh_kun, ayati and DoomLord. All the usual warnings about attempting to root a phone apply. This works on a phone with build number V16R24C, which is current as of this writing. I can't speak for any later updates.
You will need the following:
Java SDK (required for android dev kit – get the JDK): http://www.oracle.com/technetwork/java/javase/downloads/index.html
ADK: http://developer.android.com/sdk/index.html
ADB driver: http://spf.fmworld.net/oss/usb_driver/f-05d/index.html
F-05D rooting files: http://ayati.cocolog-nifty.com/blog/files/F05Droot.zip
zergRush files (tested with v4): http://forum.xda-developers.com/showthread.php?t=1319653
Optional:
- a terminal application of your choice
- busybox installer from the market
- English versions of the .bat files (remove the .txt extension): http://pastebin.com/RBCWvzES and http://pastebin.com/EQfjpDAM
Part 1, installing the ADB driver:
1. Install the JDK
2. Install the ADK
3. Go to C:\Users\YourUsername\.android and edit the adb_usb.ini file.
4. Add 0x04C5 on a separate line at the bottom. Save and close the file.
5. Reboot the computer or restart adb
6. On the phone, press home, settings, applications – toggle Unknown sources to On.
7. Same place, press development and toggle USB debugging to On.
8. Connect the phone to the PC, and when prompted, navigate to the location where you extracted the ADB driver.
Part 2, rooting the phone:
1. Extract the zergRush and rooting files to the same folder. (put the English versions in the same spot if want to use them instead).
2. With the phone connected and in debug mode, run the f05dsu.bat file (DO NOT RIGHT CLICK AND SELECT RUN AS ADMIN).
3. You first will get asked to go to Settings, Setting my body, Step/activity counter app, Pedometer use, is turned On. Press space after doing that.
4. You will then get asked to toggle the same setting OFF once, then back to ON. After doing that, press space and the phone will reboot
5. Wait for the phone to reboot and connect over USB properly. Press space when ready.
6. Files will be transferred over and the phone rooted. If you don't get any errors, press space and wait for the phone to reboot again.
7. The phone should now be rebooted, and you can install Busybox and Superuser from the market.
I had trouble getting the Busybox installers to work properly at first – the stericson one would wipe su and require re-running the f05dsu.bat, and the jrummy one would simply not start properly. I suggest trying the jrummy16 installer first just to see if it runs. In the end I had to do things manually to get it installed, but once that was done both installers worked fine.
Part 3, optional, installing Busybox manually:
1. If superuser has been lost, re-root the phone.
2. Open up your favorite terminal application and enter the following manually:
Code:
su
soff
mount -o rw,remount /system /system
dd if=/data/local/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
dd if=/data/local/su of=/system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
echo insmod /data/local/lsm_disabler.ko > /system/xbin/soff
chmod 755 /system/xbin/soff
At this point you should be able to do a "which su" and get /system/xbin/su as a response. If you don't get any response, Busybox is not properly installed (start over). Doing a "ls -ls /system/xbin/su" should also NOT return a symbolic link to Busybox – if it does, you'll need to copy over su from /data/local again. The same goes for soff. Once this is done, start up jrummy's Busybox installer to confirm the installed version of Busybox, and upgrade it if you want.
Thanks very much, worked well but sadly I managed to boot loop my phone after rooting it.
Now I need to SIM unlock the phone as the factory unlock code is gone.
F05D rooting
Hi there i have successfully rooted my Fujitsu F05D have root access but I can't seem to loads busy box, I have permission through superuser and it goes through the motions but at the end it says " install unsuccessful".
The files are in the system/bin folder but something is wrong. if I use busy box installer jrimmy16 it just say installing and keeps going and never stops if I got to to scripts and click fix file permissions
" run script" it too just spins round and round..
hmm any hints guys.
Don't do a forced install or whatever it's called, that's how I bootlooped and later SIM locked mine, still yet to send it back haha.
Hello, is this working?? I want to root my Docomo Fujitsu Arrows X F-10.. And also my phone keeps on rebooting Please help.. Any ideas why?
does it work on Fujitsu T-02D?
Hello everyone.
I have been able to modify the framework-res.apk file to enable bluetooth tethering for UAMDL from T-Mobile
While I was making the changes in there I also removed from it the call to tethering provisioning and changed the csc files needed too.
So this is for stock UAMDL T-Mobile rooted roms.
I have included the files below to install it if you want.
It does go without saying to backup everything first.
Download from Google Drive
Use the following ADB commands to successfully copy over to the framework folder. Does need to be done via ADB.
Copy new framework-res-mod.apk to root of internal sd card.
adb shell stop (this will cause the screen on your phone to go black that is fine)
adb shell mount -o remount,rw /system
adb shell cp /sdcard/framework-res-mod.apk /system/framework/framework-res.apk
adb shell chmod 644 /system/framework/framework-res.apk
adb shell start (screen will come back on and look like phone is booting again)
after that you can use your favorite root file brower to copy and replace the files customer.xml and feature.xml in the system/csc folder.
If after this you are having problems with getting google play to install apps you might need to master reset.
I want to thank elesbb for help with getting this thing to be able to be compiled and also with the adb instructions to get it copied to the phone without needing a custom recovery but just root.
Awesome man. One question though, so wireless tethering works or only bluetooth tethering?
Yes.
Wireless hotspot, bluetooth (my main goal) and wired tether are working.
Ooops I goofed in the customer.xml file with the APN used for tethering.
I used apn epc.tmobile.com when it should be epc.t-mobile.com
For the time being you can adjust that I will upload a fixed copy tomorrow when I can be at my computer again.
Actually was able to edit and reupload from phone.
It is fixed now.
Apk File not shared for download.
Sorry about that.
Should be fixed.
Give it a try again.
this is what I get
c:\windows-sdk\platform-tools>adb shell stop <<<< phone screen doesnt go black
c:\windows-sdk\platform-tools>adb shell mount -o remount,rw /system
mount: Operation not permitted
c:\windows-sdk\platform-tools>adb shell cp /sdcard/framework-res-mod.apk /system
/framework/framework-res.apk
cp: /system/framework/framework-res.apk: Read-only file system
c:\windows-sdk\platform-tools>adb shell chmod 644 /system/framework/framework-re
s.apk
Unable to chmod /system/framework/framework-res.apk: Read-only file system
am i missing something here?
Sounds like the kernel is not running in insecure mode.
Try installing and enabling insecure adbd with this app and try again
http://forum.xda-developers.com/showthread.php?t=1687590
TheArtiszan said:
Sounds like the kernel is not running in insecure mode.
Try installing and enabling insecure adbd with this app and try again
http://forum.xda-developers.com/showthread.php?t=1687590
Click to expand...
Click to collapse
Thanks man we'll give it a shot after I get off work tonight and let you know how it happens
Sent from my SGH-M919 using xda premium
So far I thought I had bluetooth working on this since it shows as a option in the tethering program but when go to pair with something it does not see or be able to use that profile for internet even though it is enabled on the phone.
Wasn't able to test at the time since I had to send in my tablet but have came to find out that this was not working.
I will continue to try and see what I missed or what I can find.
If anyone has a idea that would be helpful thank you.
Is it possible to implement mod on this Framework mate
http://www.mediafire.com/download/z98oy0q9axmcavv/framework-res.apk
Volvo Sensus Connected Touch (SCT) is a new car audio-navi system based on systems of Parrot. SCT has hardware and software from the Parrot, but is not exactly equal. In general it has some more restrictions build in by Volvo.
The system is based on the Parrot FC6100 (not the Parrot Asteroid Smart as was first believed). Looking at the Installation manual for Sensus Connected Touch (ACU) Accessory, Part Number: 31399165 the form factor is closest to the Parrot Asteroid Tablet (PAT). The only similarity that the SCT has with the PAS is Parrot's custom base of the Android 2.3 branch which is also shared by the PAT. So, if anything is more analogous to the Parrot Asteroid Tablet (PAT) than the Parrot Asteroid Smart. (thanks to Donaldta, see post) (Link to the Volvo V40 (MY14) SCT installation manual, also attached to this post as pdf)
This is how the hardware of the SCT looks if outside of the car (thanks to @AAT):
This thread is research and development on several topics and has already some nice answers:
The starting questions:
How to get ADB working y
How to install .apk files y
How to root y
WARNING!:
The below mentioned method is an experimental way of rooting. Rooting your SCT involves some android knowledge. Me, the developers and anyone in this topic are not responsible for typo's or any damage that may occur when you follow these instructions.
ROOTING means you have complete control over the android system. This also means you can do damage to it.
Security warning:
The SCT has ADB over WIFI enabled by default. Never ever connect your Volvo SCT to an unknown and/or untrusted network! Anyone connected to that same network can harm your Volvo SCT. The same applies for connecting unknown people to a known/trusted network of yours.
Security warning 2:
If your ROOTED your SCT, you are extra vulnerable to above. Anyone with ADB on the same network has complete control over your SCT!
WARNING!
Do NOT attempt to replace the SCT's BUSYBOX executable or the command symlinks to it. Another user in this forum just sent me a private message stating that they tried this on their SCT and can no longer mount USB drives or connect to ADB over WiFi. Apparently, they also do not have a File Explorer or a Terminal Emulator installed so it seems this is going to be nearly impossible to fix and will most likely be required to swap it at the dealer. See message from @donaldta : Message
The below answers are not yet completely reviewed and tested. The answers will be reviewed in the next days. In any case the instructions below are delivered "as is" and have no guaranty. If you follow the instructions below, you are responsible for your own actions. So, before you do so, understand, or at least try to, what you are doing. If you have questions or have recommendations, post them in the topic.
The answers and instructions below are constructed from the work of @gekkekoe123 and @donaldta and the trial and error experiments of the first users of the SCT (see first pages of the topic)
This means everone using these instructions must give BIG THANKS TO @gekkekoe123 and @donaldta
Instructions to root en install apps:
Note: Instructions are tested on specific versions of the Volvo SCT
It is possible that these instructions below are not (yet) working on other versions: Other continents, newer versions etc.
If you tested it on a different continent + version, let me know, so I can put it here.
Available versions:
EU
-1.47.88 - Tested
-1.47.96 - Tested
-1.49.34 Tested
One click script version 4 in attachments cmd-frama-menu-4.zip (4.62 MB)
One-click script with menu provided by @gekkekoe123 and @donaldta
Oneclick , latest version, script is discussed from here
It is rather simple as long as You have the SENSUS CONNECTED TOUCH and a PC (prefer a laptop) which You need to connect to the same network.
How to:
1. Preparing
*Download the: cmd-frama-menu-4.zip from the page 1, first post attachments. LINK: http://forum.xda-developers.com/attachment.php?attachmentid=2636951&d=1395149723
2. Follow the instructions
The instructions are rather simple.
-Connect your SCT to the same Wifi network as your PC. This wifi network can be your home network or your local hotspot from your phone.
-Unzip the (cmd-frama-menu-4.zip) and start menu.bat found in the folder "menu"
- After starting menu.bat on your pc it will ask:
Code:
Input {IP Address of Android Device} or USB:
Type in the IP address of the SCT, can be found when You go to the settings on SCT -> WIFI -> and click on the connected network (starts with 192.-).
After that the menu look list this: (Now just type in: 1 and wait a bit so it will say complete, then type in 2 and wait a bit until complete and so on, until step 6 when the SCT will restart itself)
Code:
1 - Copy Framaroot files and execute.
2 - Install remount.sh into /system/xbin and remount as writeable.
3 - Alter /system/build.prop to ro.parrot.install-all=true
4 - Install Google Framework & Android Market
5 - Install rewhitelist.sh/setpropex/patch init.parrot.capabilities.sh
6 - Reboot Android Device
7 - Install Android Packages from APKs folder.
8 - Android Debug Bridge Shell
9 - Save ADB Bugreport to Disk
R - Input connection information & retry ADB connect.
Q - Quit
Run steps 1 through 6 in order to root the SCT.
Step 7 is optional and will install all APKs you have placed inside the APKs folder in your unzipped menu.zip folder on your pc PC.
Step 8 is for manual commands or troubleshooting.
Step 9 is for troubleshooting.
Step R is only needed when the connection to the SCT seems lost.
3. You should have now a rooted SCT.
4. Installing applications
I noticed that lots of Apps from Google Play Store can not be downloaded directly to the SCT (because the SCT is not in the available list of the apps) so a easy way is to download the Applications as ".apk" files from the PC (You can find the desired app from: http://www.appsapk.com/ or http://www.androiddrawer.com/ for example).
Then copy-paste these .apk files(make sure they do not have any spaces in the filenames) to the folder "APKs" found in the downloaded unzipped folder "cmd-frama-menu-4". To install them, run the menu.bat again and once connected with the SCT again run the step 7 to install the applications You copied to the APK folder.
If you want to install apps using the Google Play Store that are larger than 7MB or so, you need to remap the cache directory to the SD card:
Code:
remount.sh cache-sd
Then after the app installation has finished, but before you start the app, remap the cache directory to the internal SCT memory:
Code:
remount.sh cache-og
5. Enable displaying applications while driving (disable safety feature)
1. Download Android Terminal Emulator from Google Play Store on Your rooted SCT.
2. Once installed, run Android Terminal Emulator under Applications
3. touch the screen - the keyboard pops up
4. Type in "su" press ENTER
5. It should ask wether You allow Superuser or not, choose the "Allow" option.
6. Type in "rewhitelist.sh" press ENTER
7. Type in "reboot" press ENTER
6. Enable Google Maps and Voice Search
First install google.maps.6.14.4.apk by the method explained above. Then copy libvoicesearch.so to /system/lib and install Voice_Search_2.1.4.apk. These files can be found in Voice_Search_2.1.4.zip.
Here is an example of how to do this with adb:
Code:
adb connect [ip of your SCT]
adb push google.maps.6.14.4.apk /mnt/sdcard
adb install /mnt/sdcard/google.maps.6.14.4.apk
adb push libvoicesearch.so /mnt/sdcard
adb shell su -c 'remount.sh system-rw'
adb shell su -c 'cp /mnt/sdcard/libvoicesearch.so /system/lib'
adb shell su -c 'chmod 644 /system/lib/libvoicesearch.so'
adb push Voice_Search_2.1.4.apk /mnt/sdcard
adb install /mnt/sdcard/Voice_Search_2.1.4.apk
Now #reboot# and Google Maps and Voice Search should be working.
Now You should be done. Happy downloading and drive safely.
Older instructions, just for reference here, do not follow anymore.
[*]One-click script with menu provided by @gekkekoe123 and @donaldta
This one-click script with menu options is here
[*]One click script for version 1.49.34: http://forum.xda-developers.com/showthread.php?p=50846498
gekkekoe123 said:
Actually it was fine (since we are in the root folder), but since I was too lazy, I used your file. I had to correct the "true" to 1.
I also changed the menu to do this. I removed the set prop option, it's not needed anymore. Setpropex should also work on older versions.
Btw, I did the upgrade manually using adb shell, and did not used the menu.bat.
So if anyone could test it or double check the menu.bat file, it should be fine. I translated the manual commands back into the menu.bat
My SCT is upgraded and I am able to install apks Let's find out if waze lost of data is fixed. Also adjusting screen dpi is still working. But we now have setpropex so we can override everything
When you finished step 5, you need to reboot in order to be able to install apks.
As allways: no guarantee and at your own risk when using the tools
Click to expand...
Click to collapse
Manual instructions and commands:
Detailed instructions how to get ADB working between your pc and SCT
Download the Android SDK, it contains the nescesary tools like ADB.exe and Monitor.bat (Download page Android SDK)
Install the android SDK
If you are using windows: set the installation path of your SDK\platform-tools\ in your windows environment variables. So, add c:\\SDK\Platform-tools\ to it. (More instructions on this point)
Now connect your SCT to a Wifi network and also connect your laptop/pc to the same wifi network. This network can be your home network, or for example the wifi network you create with your phone wifi-tether function.
Go into the SCT>Settings>Wifi and click on your connection details. Find out the IP adress of your SCT. (example, it would be something like 192.168.43.x if you are using wifi tether from your android phone. )
Now on your pc, open the command line (cmd). Easiest is to click with shift-button hold and with Right-Mouse-Button on the folder where the files reside you want to transfer to the SCT (see instructions further for rooting). After RMB click, choose option: open command line here.
Now type:
Code:
adb connect $IPADDRESS
Replace $IPADRESS with the IP from the previous step.
ADB is now connected and you are ready to type the instructions for rooting.
Code:
D:\sdk\platform-tools>adb connect 192.168.43.5
connected to 192.168.43.5:5555
Detailed instructions how to Root SCT
Download the cmd-frama-working.zip from the attachments
Attachment
Unzip it into a folder (example: d:\sct\ )
Open the commandline in this folder
Connect to adb (see instructions above)
Do the following commands (line by line):
Usage:
Code:
adb push libframalib.so /data/local/.
adb push sploit.jar /data/local/.
adb shell mkdir /data/local/tmp/dalvik-cache
adb shell ANDROID_DATA=/data/local/tmp LD_LIBRARY_PATH=/data/local dalvikvm -cp /data/local/sploit.jar com.alephzain.framaroot.FramaAdbActivity Gimli 0
[or]
adb shell ANDROID_DATA=/data/local/tmp LD_LIBRARY_PATH=/data/local dalvikvm -cp /data/local/sploit.jar com.alephzain.framaroot.FramaActivity Gimli 0
See post here and thank developer!
Now you are rooted:
Code:
cmd line frama root by Gekkekkoe
Credits to alephzain for Framalib
using Exploit: Gimli choice: 0
Executing Check
idx: 0 value: Gimli
idx: 1 value: Aragorn
Executing Check Completed
No such user 'root:root'
No such user 'root:root'
Result: 0
Test root by command:
Code:
adb shell
su
id
On the SCT you will get a screen of SuperSU, asking if shell may have root access privileges. Say yes.
exit the su and shell using
Code:
exit
exit
Reboot the SCT
If you are still within shell, just use
Code:
reboot
If you are on command line again, use
Code:
Adb Reboot
Detailed instructions how to get Google framework and Google Play (market) on the SCT
Download the files for framework and market
Framework
Market
Push them to your SCT
Code:
adb shell su root -c 'mount -o remount,rw ubi0:system /system'
adb push GoogleServicesFramework-2.2.1.apk /data/local/.
adb push Market-3.3.11.apk /data/local/.
adb shell
Now install them
Code:
cp /data/local/*.apk /system/app/.
chmod 644 /system/app/GoogleServicesFramework-2.2.1.apk
chmod 644 /system/app/Market-3.3.11.apk
reboot
After reboot, connect the SCT to internet
Open the google market on your SCT (in the applications drawer)
Log in with your google credentials
Accept terms and conditions
Be sure to stay connected to internet, google market will update itself after some minutes
Connect Adb and force SCT to reboot again.
Open Market/Play and Accept terms and conditions again! (now for the updated versions)
Wait for some time, it will again update itself again.
Open adb, force reboot again
Last time open Play (It should be named Play now, since it is updated, if it is not, wait longer and try previous steps again)
Go into My Apps, update SuperSu
After update, open SuperSu from your app drawer
It will ask to update SuperSu Binary, use Normal Method
Say thanks to Chainfire for the SuperSu
In settings, you can disable the popup that will ask if you want to run an App that is using root. Can be convenient, but also dangerous (apps can use root even without notifying you.)
Detailed instructions how to installation of other apps
We have to enable installing all apps on SCT. Warning, this means editing the build.prop, which is vital to the system. Typing errors can result in a system that will not boot correctly.
More methods apply here, use one which is convenient to you:
Fast method:
Code:
adb shell
mount -o remount,rw ubi0:system /system
sed -i 's/ro.parrot.install.allow-all=false/ro.parrot.install.allow-all=true/' /system/build.prop
Slow method, more control, moderate risk:
Code:
adb pull /system/build.prop
edit content and set to true. Content of the file should look like this
Code:
#TODO Set to false for prod #Package install limitations. Set to false to allow only the install of verified packages
ro.parrot.install.allow-all=true
replace build.prop with proper one.
Code:
adb shell su root -c 'mount -o remount,rw ubi0:system /system'
adb push build.prop /system/build.prop
If above does not work, use method like the google framework.
Third method: install ES file explorer, use the rooting functions of this app to edit build.prop
Instructions in this post and this post
Detailed instructions how to install APK files
Method 1: Use google play
Method 2: If not available on google play, use a Google Play APK downloader on your pc and install using the
Code:
ADB install
or using
ES Fileexplorer mentioned above
Detailed instructions how to make apps available during driving
All apps are behind a security wall of the SCT. When driving >5km/h, all apps not listed in the whitelist.xml will be disabled. To enable your installed apps you have to edit the whitelist.xml
Warning: it is a safety feature you are disabling now, it is your own responsability when using apps during driving
Slow method:
Get the whitelist.xml from your SCT
Code:
adb pull /system/etc/whitelist.xml
Find out which packages are installed and have to be listed there:
Code:
adb shell
pm list packages
Other method, look to the url of google play on your pc, see bold part: https://play.google.com/store/apps/details?id=com.estrongs.android.pop
List the packages by adding new lines with the package names
Edit the whitelist.xml using a smart text editor. Preferably use Notepad++
Copy the whitelist back to SCT
Code:
adb push whitelist.xml /data/local
adb shell
su
mount -o remount,rw ubi0:system /system
cp /data/local/whitelist.xml /system/etc
reboot
Scripted method:
Download script
Instructions in this post
FAQ
Audio is not working when using application X
This is a feature or limitation by design
- TomTom and other navigation apps will break Sound/Audio due to this feature.
If you have more, PM me or react in topic
TIPS
Use a USB keyboard in combination with ES file explorer or a Shell app to edit files on the system.
If you have more, PM me or react in topic
Informational links:
Information about SCT:
http://www.volvocars.com/intl/sales-services/sales/sensus-connected-touch/pages/default.aspx
Official FAQ of SCT:
http://www.volvocars.com/intl/top/support/pages/sensus-connected-touch-faq.aspx
Dutch experiences with SCT:
http://www.volvo-forum.nl/viewtopic.php?t=54935&postdays=0&postorder=asc&start=0
SCT update files:
http://www.parrot.com/nl/support/sensus-connected-touch
Current version: All regions - 1.49.34
How to unpack the update (.plf) files:
Download the plftool
Basically, download, unzip, and go into the command line, the binaries directory and use the command syntax, "plftool -i -o "
And please take the time to thank hoppy_barzed for hosting it for us and for loveshackdave for providing the tool to use it.
Linked topic of Parrot Asteroid Smart:
http://forum.xda-developers.com/showthread.php?t=2118432
Developments of other users (copied from PAS topic)
donaldta said:
Alright, I found an interesting startup script for the SCT. The path inside the archive is "FileSystem\system\etc\set_adb_usb.sh"
Code:
#!/system/bin/sh
#
# Author: Yann Sionneau <[email protected]>
#
# This script is called by a udev rule when a cable is plugged in USB0 port.
# This script sets adb.tcp.port to -1 meaning that ADB will then listen on USB
# instead of TCP/IP.
# Then this script will restart adbd service
export PATH=/system/bin:/system/xbin
if [ -f /tmp/cache/others/adb_usb ]
then
exit 0
fi
touch /tmp/cache/others/adb_usb
setprop
service.adb.tcp.port -1
stop adbd
start adbd
This leads me to believe the Android Debug Bridge (ADB) is running over TCP by default, sort of like on the original Google TV. So, you might be able to download the Android Developer Tools. Unzip it, and then at the command line use "platform-tools\adb connect <IP.address.of.SCT>" to connect to your SCT and install third party apps by either using "platform-tools\adb install <package_name>" or use the GUI, "\tools\monitor.bat" Either than or try and figure out which port on the SCT is USB 0 which turns into a ADB port when something is connected to it.
On a side note, I'm a little tired of having to respond to people about giving access to the SCT software when it is already available. The download is listed above, I fixed the link to make it even easier. All anyone needs to extract the files from the archive is the plftool that loveshackdave created and mentioned in this post.
loveshackdave said:
Okay, I've posted the binaries and source for my .NET plftool project here. I've handled the symlink sections by simply creating a file called [filename].simlink that contains the section data. The should be fine for rebuilding the plf file. I've still got to handle the file permissions byte and figure out what the 2 unknown uint's are in the file_action header. the permissions shouldn't be too much of an issue, I'm thinking of creating a filesystem meta-data file that will hold all this information for rebuilding, unless anyone has any better ideas.
Click to expand...
Click to collapse
Basically, download, unzip, and go into the command line, the binaries directory and use the command syntax, "plftool -i <input_file> -o <output_directory>"
And please take the time to thank hoppy_barzed for hosting it for us and for loveshackdave for providing the tool to use it.
Click to expand...
Click to collapse
johnnie_w said:
I succeeded in connecting to SCT over ADB. ADB is indeed enabled over TCP/IP by default. So I tried to install an apk:
Code:
C:\android\adt-bundle-windows-x86-20130911\sdk\platform-tools>adb install c:\android\apk\Framaroot-1.6.0.apk
285 KB/s (2124410 bytes in 7.265s)
pkg: /data/local/tmp/Framaroot-1.6.0.apk
Failure [INSTALL_FAILED_INVALID_APK]
Hmm, this didn't work. The logcat output:
Code:
D/AndroidRuntime( 2786): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 2786): CheckJNI is OFF
D/dalvikvm( 2786): creating instr width table
D/AndroidRuntime( 2786): Calling main entry com.android.commands.pm.Pm
D/dalvikvm( 2041): GC_EXPLICIT freed 10K, 50% free 2735K/5379K, external 2801K/3132K, paused 44ms
W/ActivityManager( 1366): No content provider found for:
W/ActivityManager( 1366): No content provider found for:
D/PackageParser( 1366): Scanning package: /data/app/vmdl-1074467422.tmp
W/PackageParser( 1366): Signatures files not found.
D/PackageManager( 1366): Scanning package com.alephzain.framaroot
W/PackageParser( 1366): Signatures files not found.
W/PackageManager( 1366): Package couldn't be installed in /data/app/com.alephzain.framaroot-1.apk
It looks like it's searching for a specific file. This is probably because installation from Unknown Sources is disabled, and I can't enable it in the sqlite database because it's not readable without root. Hmm, chicken and egg problem. Any help would be greatly appreciated!
Click to expand...
Click to collapse
donaldta said:
Okay, let's try installing something a little more legitimate than Framaroot first, since that absolutely needs the "unknown sources" to be enabled. We might have to learn how to crawl before we can run.
It seems like it is looking for the package's signature file. Try something like ESFileExplorer_120.apk or another Android Market app which should have the proper signatures inside of it. I tested it myself on the Asteroid Smart by uninstalling ES File Explorer, disabling "Unknown Sources", rebooting it, and then re-installing it via ADB.
Otherwise try other things such as "adb remount" which remounts the rootfs as writeable, "adb push <package_name.apk> /data/app" this attempts to copy the packing into the user's install directory, "adb push <package_name.apk> /data/system" this attempts to copy the package into the system. If you're used to linux command line then play around with "adb shell" to see what opportunities exists. Is this where you tried "sqlite3 /data/data/com.android.providers.settings/databases/settings.db"? If you can't do it directly, maybe copy settings.db to the sdcard and use sqlite3 to edit it then copy the modified version over? Unfortunately, I don't have a SCT so we'll need someone with one that can tinker with linux/android to help find a way.
Click to expand...
Click to collapse
Nice work
How to get ADB working?
ADB is enabled over TCP/IP by default. This means that you only need to get the IP address of the device, and you can connect to it using
Code:
adb connect $IPADDRESS
when connected to the same network. If you want to connect over USB, just plug in a USB cable in USB0 (I don'tknow yet which one this is), and ADB should switch to USB.
What can we do with ADB?
I only tried once, but I was able to get a shell. Busybox is installed, so all regular Linux commands are available. The /data directory is not accessible directly, we need root for that.
Can I just install Framaroot?
No, I wasn't able to install Framaroot directly. It complained about the signature, which is probably caused by the fact that installation from unknown sources is disabled.
So, what is the first step to be done?
I think the first step is to enable installation from unknown sources, and then install a filemanager or root the SCT. This can be done with something like:
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value=1 where name='install_non_market_apps';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
So let's try and fix this thing!
Thanks for the topic! Of course I'll be following closely!
santu001 said:
Thanks for the topic! Of course I'll be following closely!
Click to expand...
Click to collapse
Same here!
If I can be of any help (although I can't see how )
Since we can't change the setting non_market directly, android central developed a script to install without modify.
Maybe we can try this one?
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Only prerequisite is connection over ADB. No root required.
Hmm, looking into the sources it seems just a pair of batch files. I don't see magic inside it, other then a plain ADB install command.
johnnie_w said:
I think the first step is to enable installation from unknown sources, and then install a filemanager or root the SCT. This can be done with something like:
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value=1 where name='install_non_market_apps';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
So let's try and fix this thing!
Click to expand...
Click to collapse
I think the first step is to test installing packages other than Framaroot, maybe something from the Google Play Store or Asteroid Market via ADB.
getiem said:
Since we can't change the setting non_market directly, android central developed a script to install without modify.
Maybe we can try this one?
http://forums.androidcentral.com/an...-central-sideload-wonder-machine-v-1-2-a.html
Only prerequisite is connection over ADB. No root required.
Hmm, looking into the sources it seems just a pair of batch files. I don't see magic inside it, other then a plain ADB install command.
Click to expand...
Click to collapse
I believe that is because ADB is considered a "trusted source", so you can install software through it. This is how AT&T users were able to install Android Packages a long time ago while the Market app wasn't available and the "allow unknown sources" option was removed from settings. The only caveat is that the packages needs to be signed.
donaldta said:
I think the first step is to test installing packages other than Framaroot, maybe something from the Google Play Store or Asteroid Market via ADB.
Click to expand...
Click to collapse
I agree on that. I have downloaded several APK's to my laptop and will test in a few hours. I'll let you know!
johnnie_w said:
I agree on that. I have downloaded several APK's to my laptop and will test in a few hours. I'll let you know!
Click to expand...
Click to collapse
Btw, I found this topic on Stack Overflow particularly interesting.
Android Known Sources
So I have looked through the Android Open Source Project (AOSP) Source code now to see how that Unknown Sources check is done. It is more complicated than known source = android play.
So first of all for background, that Unknown Sources check and message are generated by INSTALL_NON_MARKET_APP. This flag comes up in few places, but the main place is in PackageInstallerActivity. Infact, this is the only place in AOSP where it comes up and is used to some effective degree. Let's look at that here:
Code:
String callerPackage = getCallingPackage();
if (callerPackage != null && intent.getBooleanExtra(
Intent.EXTRA_NOT_UNKNOWN_SOURCE, false)) {
try {
mSourceInfo = mPm.getApplicationInfo(callerPackage, 0);
if (mSourceInfo != null) {
if ((mSourceInfo.flags&ApplicationInfo.FLAG_SYSTEM) != 0) {
// System apps don't need to be approved.
initiateInstall();
return;
}
}
} catch (NameNotFoundException e) {
}
}
if (!isInstallingUnknownAppsAllowed()) {
//ask user to enable setting first
showDialogInner(DLG_UNKNOWN_APPS);
return;
}
initiateInstall();
So PackageInstaller is a package included with AOSP that understands how to handle the ACTION_VIEW intent for APK files. PackageInstaller checks two things before it allows an app to be installed.
That the app is a system app. If an app is a system app, it doesn't care, it tells the package manager to install your app. This means that if Samsung puts their Samsung market store as a system app on Samsung devices, then it is automatically a trusted source. Infact, it will skip step 2 here.
If that system flag is not set. If that flag is not set, and thus you are not a system app, then therefore you are not a trusted source. That being said, System apps can also skip the package installer and just go straight to calling the hidden function installPackage which can be found in PackageManagerService. This seems to be what the GooglePlayStore does, as when I disable the installation capabilities on PackageInstallerActivity I can still install apks just fine.
So to sum up: Known sources are SYSTEM APPS not just applications downloaded from google play. Google play completely circumvents the INSTALL_NON_MARKET_APP flag because it does not use the PackageInstaller. If you create an app that is not a system app, your only method for installing APKs is to use the PackageInstaller. Since your app is not a system app it will check to see if unknown sources is disabled.
Click to expand...
Click to collapse
donaldta said:
Btw, I found this topic on Stack Overflow particularly interesting.
Click to expand...
Click to collapse
There is also a second system, app verification. Does that come into play here?
http://www.androidos.in/2013/07/google-brings-verify-apps-support-to-android-2-3-or-higher/
https://support.google.com/accounts/answer/2812853?hl=en
getiem said:
There is also a second system, app verification. Does that come into play here?
http://www.androidos.in/2013/07/google-brings-verify-apps-support-to-android-2-3-or-higher/
https://support.google.com/accounts/answer/2812853?hl=en
Click to expand...
Click to collapse
As far as I know that check made during sideloading apps for devices with Android 4.2 and above. Otherwise, it is only checked via Android Market/Google Play for Android 2.3 devices and above. Since none of the Parrot devices have the Google Market it is probably a moot point. I guess Parrot / Volvo could have back ported it into the SCT and Framaroot might be picked up as Malware. But, not every app would be flagged as malware.
---------- Post added at 09:18 AM ---------- Previous post was at 08:47 AM ----------
getiem said:
Volvo Sensus Connected Touch (SCT) is a new car audio-navi system based on the Parrot Asteroid Smart (PAS). SCT differs in hardware and software from the PAS. Software looks about 90% equal, with some more restrictions build in by Volvo
Click to expand...
Click to collapse
Btw, this is a bit misleading, According to the build.prop on the SCT...
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=V01.47.88_Volvo_EU
ro.build.display.id=V01.47.88_Volvo_EU
ro.build.version.incremental=
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=mercredi 28 août 2013, 19:05:30 (UTC+0200)
ro.build.date.utc=1377709530
ro.build.type=user
ro.build.user=Parrot
ro.build.host=FR-B-800-0057
ro.build.tags=release-keys
ro.product.model=ACU Volvo
ro.product.brand=AFM
ro.product.name=fc6100_volvo
ro.product.device=fc6100_volvo
ro.product.board=fc6100-android
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Parrot
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=fc6100_volvo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=fc6100_volvo-user 2.3.7 V01.47.88_Volvo_EU release-keys
ro.build.fingerprint=AFM/fc6100_volvo/fc6100_volvo:2.3.7/V01.47.88_Volvo_EU/:user/release-keys
# end build properties
# system.prop for FC6100 Volvo
# This overrides settings in the products/generic/system.prop file
#
Click to expand...
Click to collapse
The system is based on the Parrot FC6100 not the Parrot Asteroid Smart. And looking at the Installation manual for Sensus Connected Touch (ACU) Accessory, Part Number: 31399165 the form factor is closer to the Parrot Asteroid Tablet (PAT). The only similarity that the SCT has with the PAS is Parrot's custom base of the Android 2.3 branch which is also shared by the PAT. So, if anything is more analogous to the Parrot Asteroid Tablet (PAT) than the Parrot Asteroid Smart.
donaldta said:
As far as I know that check made during sideloading apps for devices with Android 4.2 and above. Otherwise, it is only checked via Android Market/Google Play for Android 2.3 devices and above. Since none of the Parrot devices have the Google Market it is probably a moot point. I guess Parrot / Volvo could have back ported it into the SCT and Framaroot might be picked up as Malware. But, not every app would be flagged as malware.
---------- Post added at 09:18 AM ---------- Previous post was at 08:47 AM ----------
Btw, this is a bit misleading, According to the build.prop on the SCT...
The system is based on the Parrot FC6100 not the Parrot Asteroid Smart. And looking at the Installation manual for Sensus Connected Touch (ACU) Accessory, Part Number: 31399165 the form factor is closer to the Parrot Asteroid Tablet (PAT). The only similarity that the SCT has with the PAS is Parrot's custom base of the Android 2.3 branch which is also shared by the PAT. So, if anything is more analogous to the Parrot Asteroid Tablet (PAT) than the Parrot Asteroid Smart.
Click to expand...
Click to collapse
Well...good info! Another part of the puzzle
THANK YOU
Thank you very much guys for this VERY IMPORTANT thread !!
I'll follow carefully cause the SCT is really unusable at this moment with no apps and a lot bugs.
THANK YOU
@getiem
Maybe updating your opening post with the updated information!
BTW... Great Topic!
We're getting somewhere...
So thanks to all who contribute.
Yesterday I tried to install several APK's, including ES File Explorer. Unfortunately the same error message:
Code:
C:\android\adt-bundle-windows-x86-20130911\sdk\platform-tools>adb install c:\and
roid\apk\ESFileExplorer_120.apk
466 KB/s (3949829 bytes in 8.273s)
pkg: /data/local/tmp/ESFileExplorer_120.apk
Failure [INSTALL_FAILED_INVALID_APK]
I haven't tried pulling or pushing anything yet, will do that tonight.
santu001 said:
@getiem
Maybe updating your opening post with the updated information!
Click to expand...
Click to collapse
Done.
ps, I will be updating regularly the OP, but interval will be weeks, not daily or hourly. Especially weekends, I will be offline.
ps 2. Yesterday i recieved my new car with SCT. I will test the whole car first before hacking into the SCT myself.
Great
Thanks for all the efforts here. I'll be following closely
Maybe the app should be on whitlelist.xml? Try to rename the app?
I was trying to install the SCT launcher to Tablet and the catlog system says: package has no signatures matching those in shared user android.uid.system
Any methods to come over this?
jaanusj said:
Maybe the app should be on whitlelist.xml? Try to rename the app?
Click to expand...
Click to collapse
The /etc/whitelist.xml file is a list of android packages which can be running regardless of the parking brake detection. Each permutation will use the following syntax, <package name="{android.package.name}"/>, where the {android.package.name} uses the full Java-language-style package name for the application. This is listed in the APK's AndroidManifest.xml file as the "manifest package=" definition and will become the filename for the app when installed in either the /system/app or /data/app directories.
Incidentally, the java style package name also how each app is identified through the Google Play store. For example, <package name="com.tomtom.uscanada"/> can be found on Google Play via https://play.google.com/store/apps/details?id=com.tomtom.uscanada
jaanusj said:
I was trying to install the SCT launcher to Tablet and the catlog system says: package has no signatures matching those in shared user android.uid.system
Any methods to come over this?
Click to expand...
Click to collapse
Apparently, there's a way to disable signature checking by decompiling, modifying, and recompiling /system/framework/service.jar. I've never done this, so I'm not exactly comfortable with it but there are plenty of threads on XDA in regards to the topic.
There is also the Lucky Patcher app that apparently can patch core.jar to disable signature verification. It has some other security defeating functions but again, I've never used it myself so you'll have to do your own research.
Btw, when a package is complaining about "shared user", this usually points to the /data/system/packages.xml where the sharedUserId for the respective package are stored. Ultimately, this allows packages with the same sharedUserId to communicate with one another since they will be running in the same virtual machine.
johnnie_w said:
Yesterday I tried to install several APK's, including ES File Explorer. Unfortunately the same error message:
Code:
C:\android\adt-bundle-windows-x86-20130911\sdk\platform-tools>adb install c:\and
roid\apk\ESFileExplorer_120.apk
466 KB/s (3949829 bytes in 8.273s)
pkg: /data/local/tmp/ESFileExplorer_120.apk
Failure [INSTALL_FAILED_INVALID_APK]
I haven't tried pulling or pushing anything yet, will do that tonight.
Click to expand...
Click to collapse
Well, that is disappointing. I take it that you're still getting the "Signatures files not found" syntax errors from "logcat -d' while this is occuring? I'm wondering if the problem is the reverse of what jaanusj is trying to accomplish by installing AcuHome.apk on his Parrot Asteroid Tablet. And by that signatures do exist in the packages but maybe they're not being recognized as valid because the ROM isn't aware of them.
A good test for this is to install a package from the Asteroid Market, download it using "adb pull", uninstall the app, then try a "adb install" or "adb push" to reinstall it.
I tried to pull and push an APK, no luck. Pulling worked but I couldn't push it back to /system/app. We need root rights for this apparently. Also for patching the jar file or using the Lucky Patcher we need root. I'm wondering what the device is looking for. We have to find that out, maybe we can modify APK's so it does accept them. Any other ideas?
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Well, it seems Google is really retarded regarding SD Card access, changing API every other version:
http://stackoverflow.com/questions/32129716/how-does-storage-access-change-on-android-6
Radek Hulán said:
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Click to expand...
Click to collapse
i used the old Kitkat fix for my brief period on 6.0, but i rolled back to 5.1 for the time being, battery drain was too much.. here
Well, not going to root my device to gain basic features such as being able to delete photos Camera app put on SD card.
This is insane.
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Thanks Radek for this!!!
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
interesting. i see on some lines there are twrp. so this method can only be used with G4 variants that has twrp? CMIIW
i'd really like to try this on my H818P but there's no TWRP for the variant yet...
Good work mate
Requires root ?
It does not require root, but you must have unlocked bootloader.
Odesláno z mého LG-H815 pomocí Tapatalk
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Continue working this metod?
Sorry for me bad english xD
[email protected] said:
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Click to expand...
Click to collapse
Download TWRP for LG G4, run it:
https://twrp.me/devices/lgg4h815.html
In TWRP, select Mount > System, from menu, and continue according to these instructions.
ADB is part of Android SDK tools:
http://developer.android.com/sdk/index.html#Other
I don't know if it is the same problem but I believe it is, so my problem is that I can transfer files from SD to internal but it doesn't work the other way around, I don't want to unlock my bootloader so is there anything else I can do? Thanks
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Nazdar Radku,
the solution is known feature of MM (adopt external storage), but biggest dissadvantage of this, is that you cannot use SD card in other devices anymore - not only in PC using some reader, but not even in other LG-ie your lg g4 broke....no way to get your data back. For some reason LG didnt include this functionality of MM yet. 2nd disadvantage is slowing down your device, as acces, R/W ops are quite slower. And I agree with googles approach to SD card - they want to "protect" users is foolish - you cannot protect stupid people, they should make it as default but keep option for advanced users to access storage as before KK for advanced user as it could be done with KK & LP using that media_rw grp hack.
coolmaster121 said:
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Click to expand...
Click to collapse
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
rick09 said:
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
Click to expand...
Click to collapse
I resolved the issue by basically booting back in to TWIRP, flashing the stock image again. (didnt loose any files as I didnt do a wipe)
Then ran through the commands from the previous post. But the "set" did not work for me. I then downloaded the build.prop file to the desktop using the "get" command and edited it with wordpad, saved and then sent over the edited file, followed the rest of the permissions and it worked fine then.
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
rick09 said:
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
Click to expand...
Click to collapse
Just tried, it, does not seem to work. it changes the value, says I need to restart, but after restart it goes back to false
Lg G4 SD card as internal storage
Can someone tell me a little more detail on this im new to this and trying to figure it out for myself what software do I need and how to do this to my 2 lg G4's
I am running lineageOS on a rooted firestick. I am using ADB on the Firestick to control it via Homeassistant. The problem is that the adb debugging does not automatically work on reboot. Everytime i reboot i have to manually go to the menu turn off the ADB debugging and then turn in back on. After doing this i am able to reconnect adb via network (i.e, on homeassistant).
I want to ask is there any way i can use a script to automatically do this on restart of firestick. I have tried creating a script in init.d with the following contents but it doesn't seem to work.
adb tcpip 5555
I have added the following line to build.prop but this doesn't seem to work too
service.adb.tcp.port=5555
On restart the adb debugging is on in the developer tools but somehow it doesn't connect (either to Homeassistant or to my laptop), what seems to make it work is toggling it off and then back on.
Have you tried persist, so that the setting sticks between reboots?
Code:
ADB shell setprop persist.adb.tcp.port 5555
Just tried it. Still not working after reboot.
I there any command i can use to toggle the adb debugging via a startup script or crontab?
symbiansucks said:
Just tried it. Still not working after reboot.
I there any command i can use to toggle the adb debugging via a startup script or crontab?
Click to expand...
Click to collapse
Be sure you are running the above command as root user. Type su at the shell prompt, then type whoami to confirm you are root.
I guess you could make a script to run the following on each boot if the above doesn't work:
Code:
settings put global adb_enabled 1
setprop service.adb.tcp.port 5555
stop adbd
start adbd
exit 0
But I don't think this should be necessary.
Finnzz said:
Be sure you are running the above command as root user. Type su at the shell prompt, then type whoami to confirm you are root.
I guess you could make a script to run the following on each boot if the above doesn't work:
Code:
settings put global adb_enabled 1
setprop service.adb.tcp.port 5555
stop adbd
start adbd
exit 0
But I don't think this should be necessary.
Click to expand...
Click to collapse
Thanks. yes the command was run as root. Can i ask you one more thing, whats the best place to put the startup scripts in? I have tried init.d/ directory but the scripts don't get loaded from there i believe?
I have set permissions to chmod 755 for the script.
You can follow this guide,
Android (LineageOS 16) Execute Script on Start Up | sqall's blog
but it seems like there should be a much easier way to make ADB tcpip persist between reboots. I don't want to steer you wrong. @Sus_i would know better, he uses your build of LineageOS, and may have a cleaner solution.