Related
Hi,
before Oreo I happily used "Rsync for Android" to sync images from my NAS to my Pixel C (and backups the other way).
Since Oreo this no longer works. The rsync and ssh executables in /sdcard/Android/data/eu.kowalczuk.rsync4android/files/ are no longer executable, as the sdcard is mounted noexec.
The devices is rooted, stock ROM.
I am looking for either alternative apps that do not rely on executables on the sdcard or ways to make "Rsync for Android" usable again. Preferable a solution that survives system updates.
thx
afx
I am on the same boat. Any ideas?
prescaler said:
I am on the same boat. Any ideas?
Click to expand...
Click to collapse
Ok,
found something today:
Rsync Wrapper by Letscorp from the play store.
seems to work, though one needs to experiment a bit with the options.
cheers
afx
Rsync Wrapper doesn't work for me even on Nougat. One review says it may be a problem with running it on Lineage.
Could not create directory '/data/.ssh'.
Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at external/rsync/io.c(226) [sender=3.1.1]
I used llama + rsync4android to backup DCIM/Camera to my Linux server. Same problem w/ Oreo. The easiest work around is to use SmbSync2 instead. The other workaround is to use root the phone and use one of the following:
- llamaLab's Automate. (Search the community contributed tasks for an rsync example).
- Tasker + com.termux's plugin (I haven't tested this one)
The really hacker's method (My first attempt):
- install rsync4android
- install the rsync binaries (rsync, ssh, dropbearkey)
- generate dss_key
- as root, copy those binaries to to /system/bin (will need remount /system rw)
- chmod 755 those binaries
- install a cron scheduler (I used ru.kslabs.scheduler)
- create a task and directly run rsync. (Might need to run as root)
I have the same issues with rsync4android on LineageOS 15.1 (Oreo 8.1). The "really hacker's method" do not work at all. With my old, yet broken cellphone, running with CarbonROM Oreo 8.1, rsync4android worked fine.
Any ideas?
Any alternatives?
Been using rsync wrapper for quite a wile now and it works just fine (two stock Oreo systems).
Give it a try.
cheers
afx
a.f.x. said:
Been using rsync wrapper for quite a wile now and it works just fine (two stock Oreo systems).
Give it a try.
Click to expand...
Click to collapse
Thank you. I tried again with various options and for hours.
I always get this:
rsync: connection unexpectedly closed 90 bytes received so far) [Receiver]
rsync error: error in rsync protocol data stream (code 12) at external/rsync/io.c(226) [Receiver=3.1.2]
I found a solution for this issue.:
Connect the smartphone by USB to a computer.
Mount it with JMTPFS.
Write a bash script with different rsync commands.
Execute the rsync bash script.
That will do it for me. For Calendar and Contacts synchronization I use Radicale.
Still, the SD Card remains unencrypted and Adoptable SD Cards are no longer possible. I blame Google for this retrograde and insecure step.
Sorry, I was wrong. The mount with jmtpfs + rsync method did not work. Unfortunately, the files were not copied to the phone. For me this Google-FBE is a big disadvantage for Android and I have a broken smartphone, I want to get rid of it.
I faced 2 issues with rsync4android:
- The binaries didn't seem to work with Oreo
- Dropbearkey generates a DSS key instead of a RSA one
So I installed rsync wrapper and with the key it generates, it worked. But I want to be able to automate my backups with Tasker so it wbsn't perfect. So I overwrote the binaries of /data/data/eu.kowalczuk.rsync4android/files with those from /data/data/net.letscorp.rsyncwrapper/files. with the RSA key, it did work with rsync4android and Tasker
I finally got rsync wrapper to work in Lineage 15.1 by converting my dropbear formatted key to openssh format, and replacing my old rsync -e option with...
-e "ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 22 -i '/sdcard/id_rsa'"
Running LineageOS 15.1 and here is my finding:
The issue is with ssh client included in ROM. Workaround is to update the -e parameter in to include full path to local ssh instead
From: -e "ssh -l <your username>...
To: -e "/data/data/net.letscorp.rsyncwrapper/files/ssh -l <your username>...
An easy fix for Rsync Wrapper. But I was unable to edit command line for Rsync4android.
I just cannot get Rsync Wrapper to work, even playing with the options. My rsync4android command was
Code:
rsync -vHrltD --chmod=Du+rwx,go-rwx,Fu+rw,go-rw --no-perms --exclude=.trashcan --exclude=.android_secure --delete-after -e "ssh -y -p 22 -i '/sdcard/dss_key'" /storage/F975-D0D2/ [email protected]:/media/HDD/folder
I tried a number of variations including the ones you all suggested, with the end string being
Code:
rsync -vHrltD --chmod=Du+rwx,go-rwx,Fu+rw,go-rw --no-perms --exclude=.trashcan --exclude=.android_secure --delete-after -e "/data/data/net.letscorp.rsyncwrapper/files/ssh -y -p 22 -i '/sdcard/dss_key" /storage/F975-D0D2/ [email protected]:/media/HDD/folder
It just does not work: I always get as a result
Code:
/data/data/net.letscorp.rsyncwrapper/files/ssh: Exited: Error connecting: Connection refused
rsync: connection unexpectedly closed (0bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
Would you kindly suggest any other attempts I could try? My phone is not rooted, and I wish to backup my SD Card to a raspberrypi I have in my home; with Nougat it worked wonderfully and it still does from my girlfriend's Nougat phone.
Hello,
Im using MIUI 10 android 9 non rooted.
When i want activate agressive doze via adb [ adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS ], i get this error message:
D:\ANDROID\TOOLS\ADB-FASTBOOT>adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(ContextImpl.java:1822)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1850)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1391)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2118)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5604)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21860)
at android.os.Binder.shellCommand(Binder.java:629)
at android.os.Binder.onTransact(Binder.java:527)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2809)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4014)
at android.os.Binder.execTransact(Binder.java:728)
D:\ANDROID\TOOLS\ADB-FASTBOOT>
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Any help would be appreciated
exodius48 said:
Hello,
Im using MIUI 10 android 9 non rooted.
When i want activate agressive doze via adb [ adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS ], i get this error message:
D:\ANDROID\TOOLS\ADB-FASTBOOT>adb -d shell pm grant com.oasisfeng.greenify android.permission.WRITE_SECURE_SETTINGS
Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(ContextImpl.java:1822)
at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1850)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1391)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2118)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5604)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21860)
at android.os.Binder.shellCommand(Binder.java:629)
at android.os.Binder.onTransact(Binder.java:527)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2809)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4014)
at android.os.Binder.execTransact(Binder.java:728)
D:\ANDROID\TOOLS\ADB-FASTBOOT>
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Any help would be appreciated
Click to expand...
Click to collapse
Most likely your ROM is incompatible. If you are keen on Greenify, switch to a custom ROM and check.
tnsmani said:
Most likely your ROM is incompatible. If you are keen on Greenify, switch to a custom ROM and check.
Click to expand...
Click to collapse
Custom rom? So i need to unlock bootloader my device , install twrp etc etc.? OK thanks.
I dont want to do it, so better to uninstall greenify.
exodius48 said:
Custom rom? So i need to unlock bootloader my device , install twrp etc etc.? OK thanks.
I dont want to do it, so better to uninstall greenify.
Click to expand...
Click to collapse
Good plan. Greenify really isn't needed on your device/rom.
When you run ADB on the computer make sure the CMD (the black window) is running As Administrator.
It really is worth it to run these ADB commands on a Non-Rooted device, Greenify works great.
I have an OPPO K5 - China domestic version. When I tried to grant permission to GSAM I also had the same long error message. Then I discovered further down the Developer Options menu, there's a tab called "Disable Permission Monitoring", I switched it on and the adb command worked without the long error message. Not sure if MIUI has a similar tab though.
exodius48 said:
I read tutorial here https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
Click to expand...
Click to collapse
Hi.
Link is broken. Any tutorial copy to post here?
Regards.
I uninstalled com.android.updater, and fow a while everything was OK. Then today the battery was depleted, and after recharging the phone went into a bootloop. I had to install com.android.updater again, and after that everything went back to normal.
How did I find out it was com.android.updater? When in a bootloop, the Android system is actually already up and running. I was able to do adb logcat. There I saw that the system was looking for com.android.updater.
Code:
04-18 17:07:20.036 7445 7606 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-4
04-18 17:07:20.036 7445 7606 E AndroidRuntime: java.lang.RuntimeException: System error: connot find system app : com.android.updater
Note that I'm using the original China Stable ROM version 10.4.4.0(PFKCNXM), all stock, locked bootloader, not rooted. Except for the customization that we can do without root: Install Google services etc, and disable/uninstall packages through ADB.
I didn't want to upgrade to MIUI 11 because I've seen reports of it being slow and draining battery, and I want the NFC functionality, so I had to stick with China ROM.
I can't find that in my Mi 9T Pro (using the latest xiaomi.eu 20.3.27)
When I search Update I find pl.zdunex25.updater, com.android.dynsystem and com.google.android.configupdater and have all 3 frozen with SDMaid.
DeepAnger said:
I can't find that in my Mi 9T Pro (using the latest xiaomi.eu 20.3.27)
When I search Update I find pl.zdunex25.updater, com.android.dynsystem and com.google.android.configupdater and have all 3 frozen with SDMaid.
Click to expand...
Click to collapse
Oh I'm using the China Stable ROM version 10.4.4.0(PFKCNXM), sorry for not mentioning it earlier. I think custom ROMs might be immune to this sort of thing. Thanks, I've updated the post with my ROM info.
I uninstalled com.android.updater, and i cant restore it(. Do you can help me? I use redmi 4 and firmware miui_HMNote4Global_V8.5.6.0.MBFMIED_6f4b63e4fd_6.0. How i can restore one app whitout reinstall all?(
Brooont said:
I uninstalled com.android.updater, and i cant restore it(. Do you can help me? I use redmi 4 and firmware miui_HMNote4Global_V8.5.6.0.MBFMIED_6f4b63e4fd_6.0. How i can restore one app whitout reinstall all?(
Click to expand...
Click to collapse
Process of restoring generally depends on how did you 'uninstall' - please precisely describe how you did
I connect phone to computer with adb, click "debloater" and write com.android.updater in "custom" field, and click uninstall.
Brooont said:
I connect phone to computer with adb, click "debloater" and write com.android.updater in "custom" field, and click uninstall.
Click to expand...
Click to collapse
Still depending on how your debloater worked, try the folowing command(s):
adb shell cmd package install-existing com.android.updater
if it fails then:
adb shell pm enable com.android.updater
First make sure that adb connection is properly established:
adb devices
C:\adb_run\bin>adb devices
List of devices attached
NF8LHYVSNJZTGY7L recovery
C:\adb_run\bin>adb shell pm enable com.android.updater
adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: pm: not found
C:\adb_run\bin>adb shell cmd package install-existing com.android.updater
/sbin/sh: cmd: not found
C:\adb_run\bin>
Something wrong...
Brooont said:
C:\adb_run\bin>adb devices
List of devices attached
NF8LHYVSNJZTGY7L recovery
C:\adb_run\bin>adb shell pm enable com.android.updater
adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: pm: not found
C:\adb_run\bin>adb shell cmd package install-existing com.android.updater
/sbin/sh: cmd: not found
C:\adb_run\bin>
Something wrong...
Click to expand...
Click to collapse
Something wrong/strange with your adb deamon
Btw, you used certain Debloater - you should better ask in the corresponding Debloater forum/thread how to un-do
Тhanks!
wpyh said:
I uninstalled com.android.updater, and fow a while everything was OK. Then today the battery was depleted, and after recharging the phone went into a bootloop. I had to install com.android.updater again, and after that everything went back to normal.
How did I find out it was com.android.updater? When in a bootloop, the Android system is actually already up and running. I was able to do adb logcat. There I saw that the system was looking for com.android.updater.
Code:
04-18 17:07:20.036 7445 7606 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: Thread-4
04-18 17:07:20.036 7445 7606 E AndroidRuntime: java.lang.RuntimeException: System error: connot find system app : com.android.updater
Note that I'm using the original China Stable ROM version 10.4.4.0(PFKCNXM), all stock, locked bootloader, not rooted. Except for the customization that we can do without root: Install Google services etc, and disable/uninstall packages through ADB.
I didn't want to upgrade to MIUI 11 because I've seen reports of it being slow and draining battery, and I want the NFC functionality, so I had to stick with China ROM.
Click to expand...
Click to collapse
Would it be safe to disable in ADB, rather than uninstall?
Also, is it only responsible for OS updates, or does it handle things like updating the Google Play app?
hey guys..
is there any method for unrooted device..? disable commanda is not working.;
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>adb shell pm disable-user --user 0 com.android.
updater
Package com.android.updater new state: default
t-mobile_mda said:
hey guys..
is there any method for unrooted device..? disable commanda is not working.;
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>adb shell pm disable-user --user 0 com.android.
updater
Package com.android.updater new state: default
Click to expand...
Click to collapse
I would suggest not touching android.updater. it gives bootloop if disabled or uninstalled
What should we remove then
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
I think it's better to provide your questions in Redmi note 9 fourms in Xda.
Check it :https://forum.xda-developers.com/redmi-note-9
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
Redmi note 9 supporting dynamic storage if it come with android 10 out of box..if you hava fastboot rom then go to image folder on it and find super.img.
If super.img found that's mean your are good to go...
Or if you find system.img and vendor.img then sorry
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Mantipallykrishna said:
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Click to expand...
Click to collapse
If you use two GSI. That's mean you install a a dynamic GSI over a GSI then the problem will happen. Because all GSI can not capable with it. If you flash dynamic GSI over MIui Rom then the problem not happened.when you in MIui then restart to go dynamic GSI.when you are in dynamic GSI then do not reboot your device just power off and then power on your device to go MIui.then you find the dynamic GSI restart option again.even if you can not find the notification then go to your device recovery option and reboot device from recovery mood.
Even if your problem not solve then you can activate GSI from adb cmd
adb shell gsi_tool enable
Then you can go GSI and when you reboot you can not go back MIui but it is good option to use GSI without data loss.to deactivate just run this adb cmd
adb shell gsi_tool disable
Now reboot and then you can back MIui again..
But remember to check if your dynamic GSI can connect you PC via adb.
This method work for me.I also face the same problem like you.hope you can solve your problem.and remember one thing that if you use magisk patched boot.img then you can not boot your dynamic GSI.I think it is a bug hopefully it will solve soon
the first time worked fine, then i tried the command: adb shell gsi_tool enable, for some reason i wasn't able to connect to gsi with adb to turn it off: adb shell gsi_tool disable
i flashed miui with miflash, but now the installation won't start again
just found out that when a micro sd card ist in the phone, for some reason dsu won't show up, i removed the micro sd card, restarted the phone, and now dsu shows in the notification bar
Shas45558 said:
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&source=web&rct=j&url=https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list&ved=2ahUKEwj04pKZwfnrAhVLfXAKHV8FAFcQFjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Click to expand...
Click to collapse
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
fire7ly said:
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
Click to expand...
Click to collapse
Use dsu..it is easy method
Shas45558 said:
Use dsu..it is easy method
Click to expand...
Click to collapse
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
fire7ly said:
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
Click to expand...
Click to collapse
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Shas45558 said:
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Click to expand...
Click to collapse
you mean same directory where gsi present.
fire7ly said:
you mean same directory where gsi present.
Click to expand...
Click to collapse
Yes..
work in poco m3?
how about redmi note 9 pro sir? can you give me a link for the tut?
Everyting was working fine using the SHELL Command in order to remove bloatware from my device to remove any application using ANDROID 12 ONEUI 4.1.1
After updating to ONEUI 5 ANDROID 13 on December 6 2022, now im not able to get the ADB SHELL Command working it gives me and error.
Can someone let me know if there is a fix for this? like i said everything was working before upgrading to ONEUI 5 ANDROID 13
MacBook-Air platform-tools % ./adb shell
b4q:/ $ pm list packages
Exception occurred while executing 'list':
java.lang.SecurityException: Shell does not have permission to access user 150
com.android.server.am.ActivityManagerService.handleIncomingUser:14870 android.app.ActivityManager.handleIncomingUser:4802 com.android.server.pm.PackageManagerShellCommand.translateUserId:3499
at com.android.server.am.UserController.handleIncomingUser(UserController.java:2672)
at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:14870)
at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:4802)
at com.android.server.pm.PackageManagerShellCommand.translateUserId(PackageManagerShellCommand.java:3499)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellCommand.java:965)
at com.android.server.pm.PackageManagerShellCommand.runListPackages(PackageManagerShellCommand.java:861)
at com.android.server.pm.PackageManagerShellCommand.runList(PackageManagerShellCommand.java:720)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:222)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6922)
at android.os.Binder.shellCommand(Binder.java:1085)
at android.os.Binder.onTransact(Binder.java:903)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4909)
at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6906)
at android.os.Binder.execTransactInternal(Binder.java:1321)
at android.os.Binder.execTransact(Binder.java:1280)