Related
Root Galaxy Nexus (Either GSM or LTE) in Linux (Personally in Ubuntu)
Disclaimer: I am not at fault for anything you have done to your phone (ie. Brick, break, etc.). You are doing this at your own discression. I am merely stating what I did to unlock/root my phone.
Tutorial Broken Down Into Three Sections
I. Unlocking the bootloader
II. Installing Clockwork Mod Recovery
III. Installing SuperUser
Resources
1. Super User (used by flashing in Clockwork): http://download.clockworkmod.com/test/su.zip
You can get the latest version here: SuperUser by ChainsDD
2. Clockwork – based by carrier
1. Verizon (CDMA) version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.4-toro.img
MD5:*b2d31c29b7ef785f9c0802a12264d322
File size:*5,263,360*(bytes)
2. GSM version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.2-maguro.img
MD5:*445887336a863573997ccbaeedddc984
File size:*5,427,200*(bytes)
Unlocking Bootloader
Part 1: Unlock
1. First off, you need to download the adb drivers. There have been mentions of just getting the drivers, but I actually have the entire SDK. You can download it here. http://developer.android.com/sdk/index.html
2. Plug in your device, then open up Terminal (Ctrl + Alt + T) and type in: “lsusb” (without quotes). This will pull up all the devices plugged into your usb slots. Look for the one that says samsung (others have found google, but please make note).
3. Find the device, then find where it says ID. After where it says ID, it should have a number/letter mix such as “04e8” or such. Make note of that for later.
4. Go to http://developer.android.com/guide/developing/device.html . This will give the instructions on how to Install the device drivers (specific to each manufacturer). Start from where it says “4. Set up your system to detect your device.”
5. Go to your internal and cd to platform-tools. (This should include both adb and fastboot.) Put your phone into fast boot. (Do this by holding the power, volume up, and volume down buttons while phone is off).
6. Once in fastboot, go back to your computer and type in “sudo fastboot oem unlock”. This will bring up the option to unlock your phone's bootloader on your device's screen. It will give you a disclaimer, and it will say that if you unlock, it will wipe all of your phone's data. Scroll to Yes using the vol up or vol down buttons, and select it with the power button.
7. If you boot straight from there, you will go through a series of boot loops (it was 2 for me) then will be prompted to go through the process of setting up your Google account again. again.
Congratulations, your phone is now unlocked. However, this doesn't mean that you have rooted your phone.
Rooting
Part 2: Putting Clockwork Mod Recovery On Your Phone
(do step one for preparation of Part 3)
1. First, we will want to push su.zip to your phone's Internal storage or “sdcard” partition. Open up Terminal and type the command “adb push 'directory_of_su.zip'/su.zip /sdcard/”. Hit enter/return and it should transfer over. (Based on the quality of usb cord, times of transfer may vary.)
To make this easier, put su.zip into the directory of adb. Then all you have to use for the command is “adb push su.zip /sdcard/”.EDIT:
After you root, you have to delete /system/recovery-from-boot.p and reflash or else every time you reboot, the recovery partition will be written over by android. This can either be done in terminal (phone or comp) or by a file manager with root access (such as Root Explorer).
Reference: http://forum.xda-developers.com/showthread.php?t=1392336
Thanks vihil
2. Put your phone in fastboot mode again (vol up + vol down + power)
3. Go back to Terminal and type in “fastboot flash recovery 'whatever the file name is'”. This will flash CWM (Clockwork Mod) onto your phone, deleting your phone's stock recovery image.
EDIT: If it doesn't work, i.e. due to permissions, run with sudo
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.
Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Special Thanks to scary alien on androidforums.com and jcarrz1 on XDA
Reserved
Reserved......
Thanks a lot I was looking for exactly this. Appreciated. Will try in a few hours when I get my phone.
Downloaded the sdk file but have no idea what to do. My windows computer died and it would be a lot easier on that to do all this but all I have is a computer with linux currently so if anyone would be kind enough to tell me how to install sdk I'd appreciate it. I seen the read me and seen it says execute "android" first but I don't know how to do that. I realize this is incredibly annoying to the xda hive mind trust me I hate needing help like this I'm nothing close to a noob as far as rooting flashing and all that good stuff I'm just unfortunately stuck with only Linux. I'd really really appreciate it.
under the tools folder there is a script called android, u can either run it in a terminal or hopefully if u were to click it, it was ask if u want to run it!
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Seems like my fastboot is stuck on `waiting for device`. I have the fastboot screen on my GN.
Before rebooting into fastboot `adb devices` successfully showed a device (i.e., usb debugging is enabled, dunno whether it is needed for the unlocking):
$ fastboot oem unlock
< waiting for device >
Any idea?
EDIT: Found the solution. After doing a `fastboot devices` it told me "no permissions fastboot" so I needed to be root on my computer for it to work.
FadedLite said:
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Click to expand...
Click to collapse
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
C-4Nati said:
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
Click to expand...
Click to collapse
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
For simplicity, you can shorten that to: mount -o rw,remount /system
You can also delete it from a terminal on the phone or any file manager that allows root access. I think the free ES file explorer has root options.
vihil said:
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
Click to expand...
Click to collapse
for needing to type in lsusb, i found that as somewhat of a precaution. I had seen on other threads that others had their device show up as either google or samsung. So i just figured rather check first instead of installing both or something.
for the preparation, basically you do that since your phone is already on. after flashing cwm, you would have to boot back into your phone, push the file to your sdcard, then boot back into recovery. All it does is that it saves just a bit of time.
As for the sudo fastboot, I didn't actually have to do that, but i'll add it, Thanks.
As for the cwm terminal commands, i'll add that as well. Thanks again.
FadedLite said:
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Click to expand...
Click to collapse
not yet. after flashing su-bin-3.0.3.2-efghi-signed.zip (which is just the binary), the user still needs to flash Superuser-3.0.7-efghi-signed.zip, to have Superuser.apk placed in /system/app, otherwise GUI apps won't have access to su. (unless, of course, the zip you are linking here has them both)
It's preferable to have users linked to ChainsDD website, there people will find latest binaries and Superuser.apk. I also don't see any mention to him in the OP. Even if this is a tutorial, don't forget to give credit where needed.
Some help for an Ubuntu Noob/Not a Noob to Windows
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
jmartino5920 said:
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
Click to expand...
Click to collapse
Are you getting a "waiting on device" message or something similar when you run adb or fastboot?
Forget about the udev nonsense (not important really until you start developing full time) and just drop a sudo before your commands.
You can shoot me a PM or a gtalk (same username as my xda) if you want and I'd be more than happy to help you get your system going.
Thanks, still a bit more annoying that Windows but this tutorial makes it easy.
Sorry if this is ignorant, but can I use these instructions with Unix & terminal on Mac OS X? I'm thinking yes???
I rooted mine in linux as well... No problems. For some reason I was able to do it much easier though...
I did the fastboot oem unlock step above (Part 1). Rebooted then installed superuser from the android market. Then I installed Clockworkmod from the android market.
Done.
Not sure if I'm missing out on something by doing it this way but so far I've had no issues....
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?
How to enable ADB on ALLWINNER A13 9" - 4.2.2 - Windows 7 - error:device not found
Hi folks, my target is to do a full backup of my android tablet device without rooting nor installing app's on the device. It can be done just by the ADB tool and the simple command
Code:
adb backup -apk -shared -all
.
Basic information
PC: Windows 7, pro. USB 2.0 port. ADB Driver "Drivers-AllwinnerA10-32bits\32Bit_Win_7_Vista_XP" from 2011. ADB Platform-Tool, Android Debug Bridge version 1.0.31. Logged in as normal User, not Admin. The development kit is not installed, I just downloaded the Platform-Tool, unzipped it and started "adb" - I just want to make a f***ing backup :crying:
Tablet:
ALLWINNER A13 9". Android Version 4.2.2. USB Debugging enabled. Detail Info's:
Model number: JL902
Kernel Version: 3.4.0+ [email protected] #1 Mon 25.11.2013
Build-Number: full_gs702c-userdebug 4.2.2 JDQ39 eng.root.20131207
NOT ROOTED.
Problem:
I do not get a connection from the PC to the tablet. Also no RSA Key question comes up at the tablet. The adb tool just throws an error :"device not found". I tried several things, log in as Admin, "adb wait-for-device", plugging and unplugging ... nothing helped. The adb tool works fine, I tested it with a Samsung Galaxy S2. I'm not quite sure about the adb USB driver on windows, but there is no exclamation mark nor other problems reported. So this should be fine.
Anyone any hint, tip or solution? Would be great - gathering for hours with this problem - searching forum 'n stuff....
Thanks in advance
Juha
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
kramkumar said:
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
Click to expand...
Click to collapse
Thx 4 the hint, tried uberizer:
Code:
ERROR No useable device has been found
I think since in Android 4.2.2 the RSA Key authentication was introduced, something is wrong with the connection. Because I would expect the RSA Key question on the tablet, but the tablet does not show this dialog.
By the way, I recognized that the USB driver for the ADB interface is titled "Drivers-AllwinnerA10" but the tablet has a A13 core. But I do not find another driver at the moment and the vendor ID -VID_10D6&PID_0C02&REV_0202&MI_01- fits (otherwise, windows wouldn't install it anyway). Does it make sense to search for another driver?
hi from messing with various drivers and android devices i have found that installing PDA net for windows (theirs and android version too but not needed) once pdanet installs let the drivers for your phone be installed, if by any chance you have drivers already installed what you can do is go to device manager, click on your device uninstall the drivers, unplug your phone and then open pdaNET a window will come up waiting for you to connect your phone and the driver installation process will begin.
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
abstractVoid said:
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
Click to expand...
Click to collapse
Thanks for the tip. It really installed an USB driver as you said (I've deinstalled the other driver before). But sadly the result is the same. I can't access the ADB interface - same error "Device not found".
At this point I want to say thanks to all viewers of this thread, it seems really to be not an easy task. I'm still open minded in any direction and would be happy for any suggestion what I might try.
Even a hint, how I could reduce the possibilities for the root of my problem. I'm still not quite sure, if the driver is the problem or even if the tablet itself has some kind of software defect on this kernel version - By the way, does anyone have the same kernel version (posted at the beginning - 3.4.0+ [email protected] --- repeated for your convenience) of Jelly Bean (4.2.2)? Do you have experience with the ADB interface then?
How may I isolate the real problem? Any idea wellcome :cyclops:
I have nearly an identical tablet except mine has the PnP code of Vendor 10D6/Device 0C01 and it shows as P706 on the USB description.
I installed PDAnet, that actually was able to upload the Android version of PDAnet to the tablet, so I think that's a definite for the driver working. But I'm also having trouble getting ADB to list the device and I'm using the latest ADB from the SDK. Since ADB tries to setup a network server, I'm wondering if the ADB driver on windows has to be tethered as a NIC somehow?, just a theory.
I'm using a fresh install of XP and can do a complete rollback, so I'm certain it's not the OS.
There's also another quirk about this tablet. I wanted to do a backup of the firmware from this device. Techknow's utilities use ADB to issue several shell commands to copy "partitions" to the SD card, I thought I might as well try to do that manually only to find what would've been copied as /dev/block/nanda, nandb, etc. is named /dev/block/acta, actb, etc. instead. But lack of "root" means I can't read any of those partitions or even copy su into /sbin.
Uberizer isn't any good since as far as I can see that also uses ADB. Any known issues with versions of ADB? or even any other tools which do similar to ADB?, or even a way to "root" these devices just by Terminal and SD?
Regards
Ah, okey, soz I got the USB thing a bit mixed up. My tablet does have the same code, I assume the 0C01 is when it's in recovery mode (power on with volume + pressed)
I also realised the driver that was working wasn't one from PDAnet.
I've updated the working 32-bit driver with the version of ADB I'm using and included it in the attachment. Maybe you can try that and see if you have any progress.
I'll keep posted on this thread.
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
You can check what the user directory is by DIR %USERPROFILE% in the "DOS" command line (%USERPROFILE% is case sensitive).
ADB should list your device when you do adb devices in the "DOS" command line.
Basically, adb_usb.ini with a custom identifier was missing.
Regards,
qUE
Right, I've made up a pack to automate putting SU on the device and setting up permissions on SU and BUSYBOX.
!!! This is only for the VID_10D6&PID_0C02 device, your mileage may very with other devices. !!!
DRIVER directory should contain the USB driver you need, otherwise try installing PDAnet and tell it to replace the driver.
Install USB driver, run SUME.BAT
to hopefully backup all the needed stock firmware to SD;
adb shell
su
cat /dev/block/acta > /mnt/sd-ext/acta.img
cat /dev/block/actb > /mnt/sd-ext/misc.img
cat /dev/block/actc > /mnt/sd-ext/system.img
exit
exit
adb kill-server
qUE
Confirmed solved
qUE-ARM said:
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
<SNIP>
Basically, adb_usb.ini with a custom identifier was missing.
Click to expand...
Click to collapse
CONFIRMED SOLVED
Yes, that was it! I copied the adb_usb.ini file into the .android user directory (which only contains these ascii chars "0x10D6" - no CR no LF or anything else) and it worked out !!!
Thank you (Thanks meter will follow ) Some interesting things I discovered now:
There was no RSA-Key question at all on the tablet!!!
as I did the full backup with "adb backup -apk -shared -all" I was asked on the tablet to confirm this
So obviously something strange is going on here. Since it is claimed everywhere the with Android 4.2.2 the ADB interface should be generally RSA-Key protected. Okay, might be that I misunderstood something here :silly:
At least this problem is solved and I appreciated every comment in this thread. One question would be final to answer:
Who should have brought the adb_usb.ini to my PC. The ADB driver ? The ADB Platform-Tool package? So, whom to blame here - NO - just kidding :laugh:
I did briefly try the platform-tools (since I didn't mind the OS being trashed), they didn't add any adb_usb.ini and there isn't any real indication the file was needed/didn't exist, they could've simply put a note on the ADB utility when it didn't find any devices.
I'm not sure what ADB backup does. As far as I know the mounted partition images are differently named to various backup tutorials, so I get the feeling ADB backup just simply copies the user data and not much else. I recommend doing the backup I mentioned as well, it'll at least capture a copy of the boot partition, which if the device doesn't have that you'll probably need to revert to using live suite or some other firmware utility to restore it. Getting the firmware for that is another story, read a fair amount of posts here and other places on the net that don't sound fun.
I personally still can't get superuser to behave for using su on the terminal/term.apk (I want to remove useless "system" apps and make sure the device isn't talking back to anyone, i.e. google), but I'll keep tinkering.
My main aim for getting one of these tablets was to boot other firmware from the SD slot, but it looks as if the u-boot process is locked to internal NAND. So might have to modify it by adding "fatload mmc" to the script.
qUE
Quick Update;
Right the permissions thing turned out to be an issue with Superuser, dunno why. So replace the su binary from SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053) into my SUME pack and install the Superuser.apk by;
adb root
adb shell mount -o rw,remount /system
adb push Superuser.apk /system/app
as for stripping back the Applications, I've got it down to this as bare bones
adb pull /system/app backup\system\app
to backup system applications before you do anything
I found if you do delete any applications and then android gets stuck at the logo, just adb push them back and it'll boot without reboot when you've got the chain right.
minimum applications needed for boot are;
DefaultContainerService.apk
DefaultContainerService.odex
SystemUI.apk
SystemUI.odex
Launcher2.apk
Launcher2.odex
Settings.apk
Settings.odex
SettingsProvider.apk
SettingsProvider.odex
ActSensorCalib.apk
InputDevices.apk
InputDevices.odex
FusedLocation.apk
FusedLocation.odex
LatinIME.apk
LatinIME.odex
PackageInstaller.apk
PackageInstaller.odex
ApplicationsProvider.apk
ApplicationsProvider.odex
A few odds and sods missing will make settings close, but it's trivial stuff. Personally don't like the sound of Fused Location, but it won't boot without it and I haven't seen any dodgey traffic from it (yet).
I recommend installing Droidwall with adb push /system/app, before installing games.
And modifying /etc/hosts with 127.0.0.1 to certain you know whos and advertisers.
Some of my personal choice replacement applications (so far);
Total Commander over ES file explorer.
Opera Classic over the inbuilt browser (although I'm still trying to remove the default search engine).
qUE
More update;
Discovered some new things;
BACKUP FILES WITH "ADB PULL" BEFORE MODIFYING ANY FILES!!!
I think performancepolicy.apk needs to be added to the bare bones application list, afaics from looking inside the package it sets system performance stuff, so likely throttling to preserve battery power.
bin_cfg.xml in /misc which can be modified by
adb shell mount -o rw,remount /misc
then adb pull, edit and push the file back
the line in there for "backlight_brightness" 780;1020;780 can be changed to 240;1020;240 which dims the backlight substantially saving battery power. not sure if 240 is the absolute minimum, but 120 seems to be too low afaics. interestingly information on the settings is in the files named _userview.xml
build.prop in /system which can be modified by
adb shell mount -o rw,remount /system
then adb pull, edit and push the file back
and then chmod 644 /system/build.prop
the lines in there for ro.wifi.signal.level.# can all be set to 0, this theoretically cuts the wifi power usage to less than 1mW, again saving battery. if android doesn't boot fully on reboot it's because chmod hasn't been set, you should be able to adb back in and correct.
please be careful modifying either file as both seem to have safety limits imposed on certain device components (i.e. battery temprature), messing with those can make the tablet stop working.
qUE
This is debloat of Google stuff (Play and Services) / Sony / other / tracking apps etc. Updated version for Android 9 (Pie), you get better battery life and better privacy.
The main goal is mimic custom rom with fully working stock camera/connectivity/fingerprint and no Google bloat/track and as consequance, better battery life.
Root not needed for debloat, but necessary for further optimizations. (with underclocked CPUs, tuned RUN_IN_BACKGROUND privilege and BOOT_COMPLETED intent action of installed/system apps, you can reach 7 days on one charge - with deepsleep active 92% of time. /No wakelock tuning/)
Batch script reads file deb.xz1c.txt and process all lines which does not start with #. Lines/apps with starts with @ are disabled only (mainly Google components which don't like being uninstalled.)
---What You Need---
-you need working adb shell (or Flashtool), debloat_xz1c.bat and deb.xz1c.txt must be in the same directory. For example ...\Flashtool\x10flasher_lib\
-activated developer options - adb debugging
-have active screen security (pin code, password, fingerprint) so you can deactivate google as administrator app and agents of trust in settings.
-check there is no google in find my device etc.
-default Android 9 sms/mms app is Google framework dependent so you need a free alternative. QKMS is way better then default.
-install Firefox or another non-google browser. (you can enable/disable Chrome in deb.xz1c.txt)
debloat_xz1c.bat
Code:
SETLOCAL ENABLEDELAYEDEXPANSION
:: give user some time to respond to adb/root notification on phone o_o
adb devices
timeout 2
adb shell id
timeout 3
echo off
:: name of input file (deb.xz1c.txt)
for /f "eol=#" %%f in (deb.xz1c.txt) do (
set line=%%f
set fchar=!line:~0,1!
call :work_clear_data
if "!fchar!" == "@" call :work_disable
if not "!fchar!" == "@" call :work_uninst
)
goto :end
:work_clear_data
for /f "tokens=1,2 delims=^=" %%a in ("%line%") do (
echo --------[ %%b ]
echo Force-Stopping and clearing app's data:
adb shell am force-stop %%b
adb shell pm clear %%b
)
goto :eof
:work_uninst
for /f "tokens=1,2 delims=^=" %%a in ("%line%") do (
echo 'Uninstalling' app:
adb shell pm uninstall -k --user 0 %%b
)
goto :eof
:work_disable
for /f "tokens=1,2 delims=^=" %%a in ("%line%") do (
echo Disabling app:
adb shell pm disable-user %%b
)
goto :eof
:end
This is wip debloat list - minimum google stuff, no play services, sony and other. Ready for F-Droid. I am using alternative launcher/email/offline calendar/etc.
You can disable specific app without uninstalling it (place @ as first character on line).
deb.xz1c.txt
Code:
# script ignores lines starting with # ,lines(apps) starting with @ will be disabled only, lines without # or @ will be uninstalled.
# lines starting with #! and @! are important for system to function corectly. Don't remove them.
# add # to ignore
# add @ to disable
# remove # or @ to clear app's data and uninstall.
#----Sony Launcher---- (remove # if you have another launcher installed)
#/system/priv-app/home-sonyMobile-release/home-sonyMobile-release.apk=com.sonymobile.home
#----Google Chrome---- (remove # if you have another internet browser installed -Firefox,etc.. add # if you don't.)
/system/app/Chrome/Chrome.apk=com.android.chrome
#======Google Stuff======== (install another sms app first. for example QKSMS)
#!/system/app/GoogleExtShared/GoogleExtShared.apk=com.google.android.ext.shared
#!/system/app/WebViewStub/WebViewStub.apk=com.google.android.webview
#!/system/priv-app/GooglePackageInstaller/GooglePackageInstaller.apk=com.google.android.packageinstaller
#!/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk=com.google.android.gsf
@!/system/priv-app/GmsCore/GmsCore.apk=com.google.android.gms
@!/system/priv-app/CarrierServices/CarrierServices.apk=com.google.android.ims
@!/system/app/Messages/Messages.apk=com.google.android.apps.messaging
#/system/priv-app/OobConfig/OobConfig.apk=com.google.android.apps.work.oobconfig
/system/priv-app/SetupWizard/SetupWizard.apk=com.google.android.setupwizard
/system/app/ARCoreStub/ARCoreStub.apk=com.google.ar.core
/system/app/CalendarGoogle/CalendarGoogle.apk=com.google.android.calendar
/system/app/Chrome/Chrome.apk=com.android.chrome
/system/app/Drive/Drive.apk=com.google.android.apps.docs
/system/app/Duo/Duo.apk=com.google.android.apps.tachyon
/system/app/EasterEgg/EasterEgg.apk=com.android.egg
/system/app/Gmail2/Gmail2.apk=com.google.android.gm
/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk=com.google.android.syncadapters.contacts
/system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk=com.google.android.printservice.recommendation
/system/app/GoogleTTS/GoogleTTS.apk=com.google.android.tts
/system/app/Maps/Maps.apk=com.google.android.apps.maps
/system/app/Music2/Music2.apk=com.google.android.music
/system/app/Photos/Photos.apk=com.google.android.apps.photos
/system/app/Videos/Videos.apk=com.google.android.videos
/system/app/YouTube/YouTube.apk=com.google.android.youtube
/system/app/talkback/talkback.apk=com.google.android.marvin.talkback
/system/priv-app/AndroidPlatformServices/AndroidPlatformServices.apk=com.google.android.gms.policy_sidecar_aps
/system/priv-app/ConfigUpdater/ConfigUpdater.apk=com.google.android.configupdater
/system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk=com.google.android.backuptransport
/system/priv-app/GoogleFeedback/GoogleFeedback.apk=com.google.android.feedback
/system/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk=com.google.android.onetimeinitializer
/system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk=com.google.android.partnersetup
/system/priv-app/GoogleRestore/GoogleRestore.apk=com.google.android.apps.restore
/system/priv-app/HotwordEnrollmentOKGoogleWCD9340/HotwordEnrollmentOKGoogleWCD9340.apk=com.android.hotwordenrollment.okgoogle
/system/priv-app/Phonesky/Phonesky.apk=com.android.vending
/system/priv-app/Turbo/Turbo.apk=com.google.android.apps.turbo
/system/priv-app/Velvet/Velvet.apk=com.google.android.googlequicksearchbox
/system/priv-app/GoogleExtServices/GoogleExtServices.apk=com.google.android.ext.services
#----Safe to uninstall or disable----
#?/oem/priv-app/CellBroadcastReceiver/CellBroadcastReceiver.apk=com.android.cellbroadcastreceiver
#?/system/app/BluetoothMidiService/BluetoothMidiService.apk=com.android.bluetoothmidiservice
#?/system/app/CtsShimPrebuilt/CtsShimPrebuilt.apk=com.android.cts.ctsshim
#?/system/app/NfcExtension/NfcExtension.apk=com.sonymobile.nfcextension
#?/system/app/PrintSpooler/PrintSpooler.apk=com.android.printspooler
#?/system/app/SomcDualshockManager/SomcDualshockManager.apk=com.sonymobile.dualshockmanager
#?/system/app/Theme-Sou-M-cid19-silver-sw360dp-xhdpi-release/Theme-Sou-M-cid19-silver-sw360dp-xhdpi-release.apk=com.sonymobile.themes.sou.cid19.silver
#?/system/app/Theme-Sou-M-cid20-blue-sw360dp-xhdpi-release/Theme-Sou-M-cid20-blue-sw360dp-xhdpi-release.apk=com.sonymobile.themes.sou.cid20.blue
#?/system/app/Theme-Sou-M-cid21-pink-sw360dp-xhdpi-release/Theme-Sou-M-cid21-pink-sw360dp-xhdpi-release.apk=com.sonymobile.themes.sou.cid21.pink
#?/system/app/uceShimService/uceShimService.apk=com.qualcomm.qti.uceShimService
#?/system/app/UnsupportedHeadsetNotifier/UnsupportedHeadsetNotifier.apk=com.sonyericsson.unsupportedheadsetnotifier
#?/system/app/dlna-somc-xhdpi-release/dlna-somc-xhdpi-release.apk=com.sonymobile.dlna
#?/system/priv-app/CtsShimPrivPrebuilt/CtsShimPrivPrebuilt.apk=com.android.cts.priv.ctsshim
#?/system/priv-app/SemcCnapProvider/SemcCnapProvider.apk=com.sonyericsson.providers.cnap
#?/system/priv-app/SimlockUnlockApp/SimlockUnlockApp.apk=com.sonymobile.simlockunlockapp
#?/system/priv-app/assist_persistent-release/assist_persistent-release.apk=com.sonymobile.assist.persistent
#?/system/priv-app/dpmserviceapp/dpmserviceapp.apk=com.qti.dpmserviceapp
#?/system/priv-app/usb-mtp-vendor-extension-service/usb-mtp-vendor-extension-service.apk=com.sonyericsson.mtp
/system/app/AptxNotifier/AptxNotifier.apk=com.sonymobile.aptx.notifier
/system/app/BasicDreams/BasicDreams.apk=com.android.dreams.basic
/system/app/CrashMonitor/CrashMonitor.apk=com.sonyericsson.crashmonitor
/system/app/CrashMonitorSystem/CrashMonitorSystem.apk=com.sonymobile.crashmonitor.system
/system/app/ExternalKeyboardJP/ExternalKeyboardJP.apk=com.sonymobile.android.externalkeyboardjp
/system/app/FaceLock/FaceLock.apk=com.android.facelock
/system/app/IddAgent/IddAgent.apk=com.sonyericsson.idd.agent
/system/app/PartnerBookmarksProvider/PartnerBookmarksProvider.apk=com.android.providers.partnerbookmarks
/system/app/RcaHandler/RcaHandler.apk=com.sonymobile.rcahandler
/system/app/SecureClockService/SecureClockService.apk=com.sonymobile.secureclockservice
/system/app/SemcEmail-release/SemcEmail-release.apk=com.sonymobile.email
/system/app/SemcWarrantyTime/SemcWarrantyTime.apk=com.sonyericsson.warrantytime
/system/app/SomcMovieCreatorRmm-release/SomcMovieCreatorRmm-release.apk=com.sonymobile.moviecreator.rmm
/system/app/SomcPOBox-xhdpi/SomcPOBox-xhdpi.apk=com.sonymobile.pobox
/system/app/SomcXperiaServices/SomcXperiaServices.apk=com.sonymobile.xperiaservices
/system/app/SusResCheck/SusResCheck.apk=com.sonymobile.susrescheck
/system/app/SyncHub-release/SyncHub-release.apk=com.sonymobile.synchub
/system/app/Traceur/Traceur.apk=com.android.traceur
/system/app/WallpaperBackup/WallpaperBackup.apk=com.android.wallpaperbackup
/system/app/XperiaTransferMobile-release/XperiaTransferMobile-release.apk=com.sonymobile.xperiatransfermobile
/system/app/XperiaXLiveWallpaper-release/XperiaXLiveWallpaper-release.apk=com.sonymobile.xperiaxlivewallpaper
/system/app/android.autoinstalls.config.sony.xperia/android.autoinstalls.config.sony.xperia.apk=android.autoinstalls.config.sony.xperia
/system/app/app-scan3d-release/app-scan3d-release.apk=com.sonymobile.scan3d
/system/app/clock-widgets-release/clock-widgets-release.apk=com.sonymobile.advancedwidget.clock
/system/app/com.amazon.kindle/com.amazon.kindle.apk=com.amazon.kindle
/system/app/com.amazon.mShop.android.shopping/com.amazon.mShop.android.shopping.apk=com.amazon.mShop.android.shopping
/system/app/com.facebook.appmanager/com.facebook.appmanager.apk=com.facebook.appmanager
/system/app/com.facebook.katana/com.facebook.katana.apk=com.facebook.katana
/system/app/com.s.antivirus/com.s.antivirus.apk=com.s.antivirus
/system/app/com.sonyericsson.xhs/com.sonyericsson.xhs.apk=com.sonyericsson.xhs
/system/app/com.sonymobile.deqp/com.sonymobile.deqp.apk=com.sonymobile.deqp
/system/app/com.sonymobile.infoapp/com.sonymobile.infoapp.apk=com.sonymobile.infoapp
/system/app/com.sonymobile.support/com.sonymobile.support.apk=com.sonymobile.support
/system/app/com.sonymobile.xperialounge.services/com.sonymobile.xperialounge.services.apk=com.sonymobile.xperialounge.services
/system/app/com.spotify.music/com.spotify.music.apk=com.spotify.music
/system/app/fota-service/fota-service.apk=com.sonymobile.fota.service
/system/app/pip/pip.apk=com.sonymobile.pip
/system/app/update-center-config-auto-install-stub-release/update-center-config-auto-install-stub-release.apk=com.sonymobile.updatecenter.config.autoinstall
/system/app/update-center-config-late-cmz-stub-release/update-center-config-late-cmz-stub-release.apk=com.sonymobile.updatecenter.config.latecmz
/system/app/videoplaceholder/videoplaceholder.apk=com.sony.tvsideview.videoph
/system/app/weather-project-somctestkey-release/weather-project-somctestkey-release.apk=com.sonymobile.xperiaweather
/system/priv-app/AnonymousData/AnonymousData.apk=com.sonymobile.anondata
/system/priv-app/CameraWearableBridgeHandheldServer/CameraWearableBridgeHandheldServer.apk=com.sonymobile.cameracommon.wearablebridge
/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk=com.android.managedprovisioning
/system/priv-app/OMAClientProvisioning/OMAClientProvisioning.apk=com.sonyericsson.android.omacp
/system/priv-app/SemcAlbum-albumLive-release/SemcAlbum-albumLive-release.apk=com.sonyericsson.album
/system/priv-app/SemcMusic/SemcMusic.apk=com.sonyericsson.music
/system/priv-app/SomcMovieCreator-release/SomcMovieCreator-release.apk=com.sonymobile.moviecreator
/system/priv-app/StartupFlagV2/StartupFlagV2.apk=com.sonyericsson.startupflagservice
/system/priv-app/Tag/Tag.apk=com.android.apps.tag
/system/priv-app/UpdateCenter-release/UpdateCenter-release.apk=com.sonyericsson.updatecenter
/system/priv-app/com.facebook.services/com.facebook.services.apk=com.facebook.services
/system/priv-app/com.facebook.system/com.facebook.system.apk=com.facebook.system
/system/priv-app/com.sonymobile.retaildemo/com.sonymobile.retaildemo.apk=com.sonymobile.retaildemo
/system/priv-app/sonyentrance2-release/sonyentrance2-release.apk=com.sonymobile.entrance
/system/priv-app/textinput-chn-xhdpi-release/textinput-chn-xhdpi-release.apk=com.sonyericsson.textinput.chinese
/system/priv-app/usb-mtp-backup-transport/usb-mtp-backup-transport.apk=com.sonyericsson.mtp.extension.backuprestore
/system/priv-app/usb-mtp-update-wrapper/usb-mtp-update-wrapper.apk=com.sonyericsson.mtp.extension.update
/vendor/app/ChromeCustomizations/ChromeCustomizations.apk=com.android.partnerbrowsercustomizations.chromeHomepage
/vendor/app/SSGTelemetryService/SSGTelemetryService.apk=com.qualcomm.qti.qms.service.telemetry
#----Core----
#/system/app/Bluetooth/Bluetooth.apk=com.android.bluetooth
#/system/app/BookmarkProvider/BookmarkProvider.apk=com.android.bookmarkprovider
#/system/app/BuiltInPrintService/BuiltInPrintService.apk=com.android.bips
#/system/app/CameraAddonPermission-release/CameraAddonPermission-release.apk=com.sonymobile.camera.addon.permission
#/system/app/CameraCommonPermission-release/CameraCommonPermission-release.apk=com.sonymobile.cameracommon.permission
#/system/app/CameraExtensionPermission-release/CameraExtensionPermission-release.apk=com.sonyericsson.cameraextension.permission
#/system/app/CaptivePortalLogin/CaptivePortalLogin.apk=com.android.captiveportallogin
#/system/app/CarrierDefaultApp/CarrierDefaultApp.apk=com.android.carrierdefaultapp
#/system/app/CertInstaller/CertInstaller.apk=com.android.certinstaller
#/system/app/CompanionDeviceManager/CompanionDeviceManager.apk=com.android.companiondevicemanager
#/system/app/DisplayBooster/DisplayBooster.apk=com.sonymobile.displaybooster
#/system/app/FidoCryptoService/FidoCryptoService.apk=com.qualcomm.qti.auth.fidocryptoservice
#/system/app/FingerprintExtensionService/FingerprintExtensionService.apk=com.fingerprints.extension.service
#/system/app/HTMLViewer/HTMLViewer.apk=com.android.htmlviewer
#/system/app/IddPermissionApplicationCertificate/IddPermissionApplicationCertificate.apk=com.sonymobile.idd.permission.application_certificate
#/system/app/Iengine/Iengine.apk=com.sonymobile.intelligent.iengine
#/system/app/ImageProcessorPermission-release/ImageProcessorPermission-release.apk=com.sonymobile.imageprocessor.permission
#/system/app/IntelligentObserver/IntelligentObserver.apk=com.sonymobile.intelligent.observer
#/system/app/KeyChain/KeyChain.apk=com.android.keychain
#/system/app/LiveWallpapersPicker/LiveWallpapersPicker.apk=com.android.wallpaper.livepicker
#/system/app/ManagedConfigAdminStub-release/ManagedConfigAdminStub-release.apk=com.sonymobile.enterprise.managedconfigadmin
#/system/app/NfcNci/NfcNci.apk=com.android.nfc
#/system/app/PacProcessor/PacProcessor.apk=com.android.pacprocessor
#/system/app/QtiTelephonyService/QtiTelephonyService.apk=com.qualcomm.qti.telephonyservice
#/system/app/SecureElement/SecureElement.apk=com.android.se
#/system/app/SemcAutoPowerOff/SemcAutoPowerOff.apk=com.sonyericsson.autopoweroffservice
#/system/app/SemcClock-somclive-release/SemcClock-somclive-release.apk=com.sonyericsson.organizer
#/system/app/SemcSettings/SemcSettings.apk=com.sonyericsson.settings
#/system/app/SemcSimDetection/SemcSimDetection.apk=com.sonyericsson.simdetection
#/system/app/ServiceMenu/ServiceMenu.apk=com.sonyericsson.android.servicemenu
#/system/app/SimAppDialog/SimAppDialog.apk=com.android.simappdialog
#/system/app/SimSettings/SimSettings.apk=com.qualcomm.qti.simsettings
#/system/app/SmartPrediction/SmartPrediction.apk=com.sonymobile.prediction
#/system/app/SomcExtGps/SomcExtGps.apk=com.sonymobile.gps.extension
#/system/app/SoundEnhancement/SoundEnhancement.apk=com.sonyericsson.soundenhancement
#/system/app/Stk/Stk.apk=com.android.stk
#/system/app/TetherEntitlementCheck/TetherEntitlementCheck.apk=com.sonyericsson.tetherentitlementcheck
#/system/app/TransmitPower/TransmitPower.apk=com.sonymobile.transmitpower
#/system/app/WAPPushManager/WAPPushManager.apk=com.android.smspush
#/system/app/XperiaConfigurator-release/XperiaConfigurator-release.apk=com.sonymobile.deviceconfigtool
#/system/app/btidd/btidd.apk=com.sonymobile.btidd
#/system/app/com.swiftkey.swiftkeyconfigurator/com.swiftkey.swiftkeyconfigurator.apk=com.swiftkey.swiftkeyconfigurator
#/system/app/com.touchtype.swiftkey/com.touchtype.swiftkey.apk=com.touchtype.swiftkey
#/system/app/datastatusnotification/datastatusnotification.apk=com.qti.qualcomm.datastatusnotification
#/system/app/device-monitor/device-monitor.apk=com.sonyericsson.devicemonitor
#/system/app/embms/embms.apk=com.qualcomm.embms
#/system/app/externalkeyboardsinternational-release/externalkeyboardsinternational-release.apk=com.sonymobile.android.externalkeyboard
#/system/app/skin-core-release/skin-core-release.apk=com.sonymobile.runtimeskinning.core
#/system/app/skin-effects-release/skin-effects-release.apk=com.sonymobile.runtimeskinning.effects
#/system/app/skin-picker-release/skin-picker-release.apk=com.sonymobile.runtimeskinning.picker
#/system/app/smtofrgbc/smtofrgbc.apk=com.sonymobile.smtofrgbc
#/system/app/white-balance/white-balance.apk=com.sonymobile.whitebalance
#/system/framework/framework-res.apk=android
#/system/priv-app/ApnUpdater/ApnUpdater.apk=com.sonymobile.apnupdater
#/system/priv-app/ArtFilterCamera-xhdpi-release/ArtFilterCamera-xhdpi-release.apk=com.sonyericsson.android.addoncamera.artfilter
#/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk=com.android.backupconfirm
#/system/priv-app/BlockedNumberProvider/BlockedNumberProvider.apk=com.android.providers.blockednumber
#/system/priv-app/CNEService/CNEService.apk=com.quicinc.cne.CNEService
#/system/priv-app/CalendarProvider/CalendarProvider.apk=com.android.providers.calendar
#/system/priv-app/CallLogBackup/CallLogBackup.apk=com.android.calllogbackup
#/system/priv-app/CameraCommon/CameraCommon.apk=com.sonymobile.cameracommon
#/system/priv-app/CameraPanorama-release/CameraPanorama-release.apk=com.sonyericsson.android.camera3d
#/system/priv-app/CarrierConfig/CarrierConfig.apk=com.android.carrierconfig
#/system/priv-app/Contacts/Contacts.apk=com.sonymobile.android.contacts
#/system/priv-app/ContactsProvider/ContactsProvider.apk=com.android.providers.contacts
#/system/priv-app/CoreSettings/CoreSettings.apk=com.sonymobile.coresettings
#/system/priv-app/CustomizationSelector/CustomizationSelector.apk=com.sonymobile.customizationselector
#/system/priv-app/CustomizedSettings/CustomizedSettings.apk=com.sonyericsson.customizedsettings
#/system/priv-app/DefaultContainerService/DefaultContainerService.apk=com.android.defcontainer
#/system/priv-app/DeviceSecurityService/DeviceSecurityService.apk=com.sonymobile.devicesecurity.service
#/system/priv-app/Dialer2/Dialer2.apk=com.sonymobile.android.dialer
#/system/priv-app/DocumentsUI/DocumentsUI.apk=com.android.documentsui
#/system/priv-app/DownloadProvider/DownloadProvider.apk=com.android.providers.downloads
#/system/priv-app/DownloadProviderUi/DownloadProviderUi.apk=com.android.providers.downloads.ui
#/system/priv-app/EmergencyInfo/EmergencyInfo.apk=com.android.emergency
#/system/priv-app/EnterpriseService/EnterpriseService.apk=com.sonymobile.enterprise
#/system/priv-app/EnterpriseSystemService/EnterpriseSystemService.apk=com.sonymobile.enterprise.service
#/system/priv-app/ExternalStorageProvider/ExternalStorageProvider.apk=com.android.externalstorage
#/system/priv-app/FusedLocation/FusedLocation.apk=com.android.location.fused
#/system/priv-app/GetSetClient-release/GetSetClient-release.apk=com.sonymobile.getset
#/system/priv-app/GetSetSystem-release/GetSetSystem-release.apk=com.sonymobile.getset.priv
#/system/priv-app/ImageEnhancer/ImageEnhancer.apk=com.sonymobile.imageenhancer
#/system/priv-app/InputDevices/InputDevices.apk=com.android.inputdevices
#/system/priv-app/IntelligentBacklight/IntelligentBacklight.apk=com.sonymobile.intelligent.backlight
#/system/priv-app/IntelligentGesture/IntelligentGesture.apk=com.sonymobile.intelligent.gesture
#/system/priv-app/LockscreenSettings-common-release/LockscreenSettings-common-release.apk=com.sonyericsson.lockscreen.uxpnxt
#/system/priv-app/MediaProvider/MediaProvider.apk=com.android.providers.media
#/system/priv-app/MmsService/MmsService.apk=com.android.mms.service
#/system/priv-app/MtpDocumentsProvider/MtpDocumentsProvider.apk=com.android.mtp
#/system/priv-app/MusicFX/MusicFX.apk=com.android.musicfx
#/system/priv-app/NfcExtraResources/NfcExtraResources.apk=com.sonymobile.nfcextension.nfcextraresources
#/system/priv-app/ProxyHandler/ProxyHandler.apk=com.android.proxyhandler
#/system/priv-app/RemoteUnlockService/RemoteUnlockService.apk=com.sonymobile.simlock.service
#/system/priv-app/SEMCSetupWizard/SEMCSetupWizard.apk=com.sonyericsson.setupwizard
#/system/priv-app/SemcCameraUI-xhdpi-release/SemcCameraUI-xhdpi-release.apk=com.sonyericsson.android.camera
#/system/priv-app/SemcPhotoEditor/SemcPhotoEditor.apk=com.sonyericsson.photoeditor
#/system/priv-app/SemcPowerSaveModule/SemcPowerSaveModule.apk=com.sonyericsson.psm.sysmonservice
#/system/priv-app/SemcStorageChecker/SemcStorageChecker.apk=com.sonymobile.storagechecker
#/system/priv-app/SemcTelephonyProvider/SemcTelephonyProvider.apk=com.android.providers.telephony
#/system/priv-app/Settings/Settings.apk=com.android.settings
#/system/priv-app/SettingsIntelligence/SettingsIntelligence.apk=com.android.settings.intelligence
#/system/priv-app/SettingsProvider/SettingsProvider.apk=com.android.providers.settings
#/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk=com.android.sharedstoragebackup
#/system/priv-app/Shell/Shell.apk=com.android.shell
#/system/priv-app/SmartCharger-release/SmartCharger-release.apk=com.sonymobile.smartcharger
#/system/priv-app/SmartCleaner/SmartCleaner.apk=com.sonymobile.smartcleaner
#/system/priv-app/SomcColorGamut/SomcColorGamut.apk=com.sonymobile.colorgamut
#/system/priv-app/SomcExtTelephony/SomcExtTelephony.apk=com.sonymobile.telephony.extension
#/system/priv-app/SomcGloveMode/SomcGloveMode.apk=com.sonymobile.glovemode
#/system/priv-app/SomcIndeviceIntelligence-release/SomcIndeviceIntelligence-release.apk=com.sonymobile.indeviceintelligence
#/system/priv-app/SomcWifiDisplay/SomcWifiDisplay.apk=com.sonymobile.tvout.wifidisplay
#/system/priv-app/SomcWifiService/SomcWifiService.apk=com.sonymobile.wifi
#/system/priv-app/SoundPhotoCamera-xhdpi-release/SoundPhotoCamera-xhdpi-release.apk=com.sonymobile.android.addoncamera.soundphoto
#/system/priv-app/StatementService/StatementService.apk=com.android.statementservice
#/system/priv-app/StorageManager/StorageManager.apk=com.android.storagemanager
#/system/priv-app/SuperStamina/SuperStamina.apk=com.sonymobile.superstamina
#/system/priv-app/SwiqiSystemService/SwiqiSystemService.apk=com.sonymobile.swiqisystemservice
#/system/priv-app/SystemUI/SystemUI.apk=com.android.systemui
#/system/priv-app/TeleService/TeleService.apk=com.android.phone
#/system/priv-app/Telecom/Telecom.apk=com.android.server.telecom
#/system/priv-app/TelephonyThermalCheck/TelephonyThermalCheck.apk=com.sonymobile.telephonythermalcheck
#/system/priv-app/TimeShiftCamera-release/TimeShiftCamera-release.apk=com.sonymobile.android.addoncamera.timeshift
#/system/priv-app/USMHome/USMHome.apk=com.sonymobile.usm
#/system/priv-app/UserDictionaryProvider/UserDictionaryProvider.apk=com.android.providers.userdictionary
#/system/priv-app/VpnDialogs/VpnDialogs.apk=com.android.vpndialogs
#/system/priv-app/WallpaperCropper/WallpaperCropper.apk=com.android.wallpapercropper
#/system/priv-app/WfdService/WfdService.apk=com.qualcomm.wfd.service
#/system/priv-app/assist_app-release/assist_app-release.apk=com.sonymobile.assist
#/system/priv-app/com.qualcomm.location/com.qualcomm.location.apk=com.qualcomm.location
#/system/priv-app/enhancedusbux/enhancedusbux.apk=com.sonyericsson.usbux
#/system/priv-app/ims/ims.apk=org.codeaurora.ims
#/system/priv-app/qcrilmsgtunnel/qcrilmsgtunnel.apk=com.qualcomm.qcrilmsgtunnel
#/vendor/app/ConnectionSecurityService/ConnectionSecurityService.apk=com.qualcomm.qti.qms.service.connectionsecurity
#/vendor/app/TimeService/TimeService.apk=com.qualcomm.timeservice
---Important---
You can go back if you screw something
to enable disabled app
Code:
adb shell pm enable <name of package>
to install "uninstalled" app
Code:
adb shell cmd package install-existing <name of package>
my setup: xZ1c stock G8441_47.2.A.11.228, Android 9 + Magisk 20.1 + TWRP 3.3.1
This seems like a good thread to ask.
I went a step further to debloat my XZ1C and deleted all the apks that I thought were unnecessary.
Unfortunately i I deleted the apk responsible for the video editor (the one that pops up for example after taking a 120fps video with the stock camera app). I thought the apk was the one for the movie creator but instead it was the video editor.
I wish for a kind soul to
1. Tell me the package name of the video editor so I won't delete it again.
2. Upload the untouched apk for me so that I can restore it \ tell me how to extract it from the original ftf
reserved for rooted devices optimizations
It removed Play store.
OP thanks for posting this. I think I might try it out. I currently have Lineage 16 on my XZ1 Compact but it has issues with 5Ghz wifi and in my circumstance, I need to put on airplane mode for the GPS to work.
100% newb question - how do I run the script in adb? I've used adb to disable/enable apps but how do I run a batch file? I tried to find answers online but no solid answers.
Edit: found the answer - I double clicked the bat file.
@megaice
"Root not needed for debloat, but necessary for further optimizations. (with underclocked CPUs, tuned RUN_IN_BACKGROUND privilege and BOOT_COMPLETED intent action of installed/system apps, you can reach 7 days on one charge - with deepsleep active 92% of time. /No wakelock tuning/) "
Are this further optimization implemented?
Sent from my [device_name] using XDA-Developers Legacy app
After applying this debloating script, I lag when I go to bluetooth > connection preferences, it works but freezer for 10 seconds, solution?
Edit: Installing uninstalled apps doesn't work, or how to get it work exactly? Use app path or just package name? Does apk has to be on PC or not? Need explanation :/
@megaice thanks for this script.
is it possible to modify the script so it uninstalls the app for all users, not just current or default user?
how to add packages to the script? i have some packages in my version of stock rom, e.g. Prime Video, for which I can't locate the package in /system/app or /system/priv-app
thanks!
wyt18 said:
@megaice thanks for this script.
is it possible to modify the script so it uninstalls the app for all users, not just current or default user?
how to add packages to the script? i have some packages in my version of stock rom, e.g. Prime Video, for which I can't locate the package in /system/app or /system/priv-app
thanks!
Click to expand...
Click to collapse
Hi There,
1) script curently "uninstalls" app for all users, it uninstall it for user 0 (user 0 = root), so all users are affected.
2) you can list and sort installed packages in you rom by android shell command "pm list packages -f". switch -f means show install path. Some examples are here.
Frano35 said:
After applying this debloating script, I lag when I go to bluetooth > connection preferences, it works but freezer for 10 seconds, solution?
I am using bluetooth with BT repro/audio on car and home system without a problem. Did you try connect to other BT hardware?
Edit: Installing uninstalled apps doesn't work, or how to get it work exactly? Use app path or just package name? Does apk has to be on PC or not? Need explanation :/
Click to expand...
Click to collapse
If you want back uninstalled app, you can enable it by "adb shell cmd package install-existing <package_name_of_app>". The app is still on rom in your phone, just deactivated.
[email protected] said:
@megaice
Are this further optimization implemented?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi, not in .bat files. It's hand work with 2-3 applications. i want to do a bash script, but had no time for it. (family, RL) maybe later.
techno-viking said:
OP thanks for posting this. I think I might try it out. I currently have Lineage 16 on my XZ1 Compact but it has issues with 5Ghz wifi and in my circumstance, I need to put on airplane mode for the GPS to work.
100% newb question - how do I run the script in adb? I've used adb to disable/enable apps but how do I run a batch file? I tried to find answers online but no solid answers.
Edit: found the answer - I double clicked the bat file.
Click to expand...
Click to collapse
Hi Techno-wiking.
Yea, just double bash it with your sword. Btw. you nickname brings back (video) memories....
andacro said:
It removed Play store.
Click to expand...
Click to collapse
Hi there.
Yea, it's feature. You can edit the script and enable google bloat if you want.
megaice said:
Hi There,
1) script curently "uninstalls" app for all users, it uninstall it for user 0 (user 0 = root), so all users are affected.
2) you can list and sort installed packages in you rom by android shell command "pm list packages -f". switch -f means show install path. Some examples are here.
Click to expand...
Click to collapse
thanks! I still see the apk files of the system apps I "uninstalled" when browsing my root folder at /system/app though. and total storage space used has not changed. is that meant to happen?
wyt18 said:
thanks! I still see the apk files of the system apps I "uninstalled" when browsing my root folder at /system/app though. and total storage space used has not changed. is that meant to happen?
Click to expand...
Click to collapse
Yes, as all it's doing is disabling, you're better off using Titanium Backup or you can use the pm uninstall -k --user 0 com.insertapp.name if you have root to remove them completely.
SXUsr said:
Yes, as all it's doing is disabling, you're better off using Titanium Backup or you can use the pm uninstall -k --user 0 com.insertapp.name if you have root to remove them completely.
Click to expand...
Click to collapse
thanks - i do have root and plan to try this approach, but would doing this make safetynet fail?
SXUsr said:
Yes, as all it's doing is disabling, you're better off using Titanium Backup or you can use the pm uninstall -k --user 0 com.insertapp.name if you have root to remove them completely.
Click to expand...
Click to collapse
just tried this but it does not uninstall - it surfaces an error and then does nothing. I'm also not able to uninstall using Titanium backup. Not sure why but I am on stock rom with magisk root, nothing special
wyt18 said:
just tried this but it does not uninstall - it surfaces an error and then does nothing. I'm also not able to uninstall using Titanium backup. Not sure why but I am on stock rom with magisk root, nothing special
Click to expand...
Click to collapse
Try adb shell first then the command.
SXUsr said:
Try adb shell first then the command.
Click to expand...
Click to collapse
yes, have already tried that of course ... error message says cannot uninstall. might be due to the internal drive being encrypted?
Great work! Saved me a lot of time looking for these unwanted package names.
However, the script broke my themes app. Sometimes it even shows a "has stopped" message.
Is this intentional or something went wrong? Which disabled app has to be re-enabled to fix it? Can't really find anything that could stop it from working.
I attached the customized "deb.xz1c.txt" file I've used.
Bash version of the script:
Code:
#!/bin/bash
set -eu
exec 3< ${1:-deb.xz1c.txt}
while read -u 3 LINE; do
[[ $LINE =~ ^#|^$ ]] && continue
APP=${LINE##*=}
echo ======= $APP =======
adb shell am force-stop $APP
adb shell pm clear $APP
if [[ $LINE =~ ^@ ]]; then
adb shell pm disable-user $APP ||:
else
adb shell pm uninstall -k --user 0 $APP ||:
fi
done
I'm running on the 10.5.10.IN11BA build.
Just get a command shell to your OnePlus 8 Pro through adb, no need for the device to be rooted or anything.
Once you get there, just type:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It will launch the FactoryMode app and get you directly to the manual camera test view.
Just press the bottom right icon until you get to the color filter.
I have no doubt there is easier and quicker ways to get the same result, maybe through an apk.
Edit:
As far as I know, this workaround could work on any OnePlus 8 Pro model.
Also, as pointed out by ster88, you also can take videos with the filter, which was not possible with the camera app.
I tried not working. I used th terminal app from google playstore.
Can u specifically provide which app and where.
And anything to enable on developer mode.
sajjadhussaini said:
I tried not working. I used th terminal app from google playstore.
Can u specifically provide which app and where.
And anything to enable on developer mode.
Click to expand...
Click to collapse
Sure !
To enable developper mode, go to "Settings > About phone" and tap the "Build number" until they tell you have developper mode enabled.
Then go to "Settings > System > Developper options" and under "Debugging" enable "USB Debugging" and "Wireless ADB Debugging".
Once that is done, on your computer, download the platform-tools, containing adb here :
Code:
https://developer.android.com/studio/releases/platform-tools
Once it is downloaded, go inside it with your command line.
If you are doing this wirelessly, get your phone IP address and type:
Code:
adb connect <your-phone-ip-address>
Then if it worked, to know what the transport id of our device is, type :
Code:
adb devices -l
Once you have the transport id, type this to get a shell to your phone:
Code:
adb -t <transport-id> shell
You can get more details on how adb works here:
Code:
https://developer.android.com/studio/command-line/adb
Then when you have access to the shell, just type:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
If everything went fine, you should get access to the camera !
I could not use a terminal app to run the command, usually because the terminal app doesn't want to let the camera application to take over the view, or something like that, not sure.
The ideal would be to have a dedicated apk to run the command, at least for the time being.
Tried to launch using an app called Activity launcher and it didn't work.
play.google.com/store/apps/details?id=de.szalkowski.activitylauncher
imgur.com/a/BS9Wqzc
I'm not rooted, are you sure this works for non rooted devices? I'll try later with adb to see what happens.
Here is the error from Termux. Hope it can be loaded via apk, not sure if it suffers same restrictions:
$ am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
From what I understood, you need to run the command from an adb shell. You cannot run it from within the phone as far as I know.
You can still run it from adb and "lock" the application so it stays in the background.
And I tried with multiple Terminal apps, the command works with none of them (Termux, Terminal Emulator, Material Terminal, etc...)
Apparently, you have some rights on the adb command shell that you don't get as a simple user on the phone.
You man are genius. I found easy way also to keep it running if needed. After getting the camera test to run, you can lock the app so phone will not close it and always return to it. Thanks, finally I can enjoy my camera
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
lllsondowlll said:
Here is the error from Termux. Hope it can be loaded via apk, not sure if it suffers same restrictions:
$ am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
Did you get any solution for this ?
aishkumar said:
Did you get any solution for this ?
Click to expand...
Click to collapse
...
lllsondowlll said:
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Click to expand...
Click to collapse
I've made a script that allows you to launch the Camera from your phone by just typing ./camera in Termux. No root needed. It can be found here: https://github.com/lllsondowlll/OP8_Camera/blob/master/README.md
can u make a video on this how u used termux and what to do whole process screen recording will be helpful coz i am new to this and i dnt wanna mess up with my phone if i lost some files or smthing please make a video i really want to play with IR camera
It works but not really required
It's working, but have few questions to myself.
1. Does it really needed?
Ans: No, you won't keep clicking pics of plastic material to see inside.
2. Is it handy?
Ans: yes, once opened you can pin/lock it in recent app and open whenever required.
It is just a IR camera and nothing wrong in it, I believe OP will enable it in future, because it really doesn't show through the clothes and even if you want to see for some black thin clothes, you need to go near.
So if you are thinking to click the nude people and go closure you will be slapped.
Few images I have taken.
babsvsphudi said:
can u make a video on this how u used termux and what to do whole process screen recording will be helpful coz i am new to this and i dnt wanna mess up with my phone if i lost some files or smthing please make a video i really want to play with IR camera
Click to expand...
Click to collapse
https://youtu.be/iVQYu-CeN24
You can't hurt anything. Just follow the instructions.
lllsondowlll said:
You can't hurt anything. Just follow the instructions.
Click to expand...
Click to collapse
thanks man you are awesome love n respect for u brother
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Error type 3
Error: Activity class {com.oneplus.factorymode/com.oneplus.factorymode.camera.manualtest.CameraManualTest} does not exist.
connected to localhost:5555
error: more than one device/emulator
I ran it as the video shows. But I got an error like above.
Is there any way to solve this problem or is it not possible with IN2020? Please forgive me for using a translator.
pcningen said:
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Error type 3
Error: Activity class {com.oneplus.factorymode/com.oneplus.factorymode.camera.manualtest.CameraManualTest} does not exist.
connected to localhost:5555
error: more than one device/emulator
I ran it as the video shows. But I got an error like above.
Is there any way to solve this problem or is it not possible with IN2020? Please forgive me for using a translator.
Click to expand...
Click to collapse
I was able to resolve this issue by reinstalling factory mode. I apologize to you for a fuss over. Many thanks to the developers of this method.
Since I can't get termux to work for now, another idea if you want to have it accessible all the time(*), is to run this (beautiful) command with an adb shell from a computer and then lock the app so you can't accidentally close it.
After that you can always go back to it whenever you want it!
*App won't remain locked after reboot, obviously.
lllsondowlll said:
Launched it without a computer by using ADB from temux
--no root required
https://github.com/MasterDevX/Termux-ADB
*Enable wireless debugging (wireless doesn't actually need to be on)
Note wireless debugging --takes some time to take effect, sometimes up to 3-5 minutes for me.
*Run the installer above in termux,
*Type adb devices
*Type adb connect 127.0.0.1
*Accept the trusted key
*type adb shell
Troubleshooting:
*If you get an error about multiple devices type adb kill-server
*type adb devices
*type adb shell
*Accept the trusted key
*then paste in: am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
Click to expand...
Click to collapse
I wanna piggyback on this some, since this is similar to the process I just did.
So while this works for nonroot users (I didn't actually test the nonroot version myself), if you are rooted, AND using magisk, I personally install ADB and fastboot binaries from the repo from zackptg5(?) And then just told termux to run an elevated shell (su) and then pasted in the command linked in OP:
Code:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
It then loaded the testmode camera app, and (xXx caused it to crash, I had to disable it but I don't know if it's a setting with my config) voila. It worked! Thank you.
Edit: I wanna say just running termux in root would solve the issue either way still, but, my point still is there.