Hi guys so recently i decided to change my Recovery and Firmware on my Xperia Z5 dual (E6683) i decided to flash Lineage OS 17.1 UNOFFICIAL-SUMIRE after that i decided to flash both GAPPS and Magisk But theres an issue "PERMISSION ISSUE" on GAPPS andriod setup i did manage to get it working via these steps hope this helps you
Requirements:
Windows/Mac with ADB installed
Phone (guessing you have TWRP and Lineage installed)
USB cable (obviously you will need this)
ADB SHELL COMMAND FOR SYSTEM UI HAS STOPPED WORKING/ANDRIOD SETUP HAS STOPPED WORKING (LINEAGE OS 17.1 ANDRIOD 10 Q)
FIX:
1ST INSTALL LINEAGE OS THROUGH TWRP RECOVERY (DO NOT INSTALL GAPPS FIRST!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2ND REBOOT DEVICE
3RD SETUP THE DEVICE AS NORMAL THEN AFTER THAT GO TO SETTING>ABOUT PHONE TAP BASEBAND VERSION 4 TIMES TO UNLOCK DEVELOPER MODE
4TH GO TO SETTINGS>SYSTEM>DEVELOPER OPTIONS THEN FIND USB DEBUGGING ENABLE IT
5TH REBOOT DEVICE TO RECOVERY
6TH INSTALL GAPPS
7TH REBOOT TO SYSTEM
8TH OPEN CMD AND TYPE cd C:\Users\(username)\(file directory)\adb CLICK ENTER
9TH TYPE COMMANDS DOWN BELOW....
STAT REPORT:adb shell dumpsys package com.google.android.setupwizard
FIX CMD
adb shell pm grant com.google.android.setupwizard android.permission.CALL_PHONE
adb shell pm grant com.google.android.setupwizard android.permission.GET_ACCOUNTS
adb shell pm grant com.google.android.setupwizard android.permission.PROCESS_OUTGOING_CALLS
adb shell pm grant com.google.android.setupwizard android.permission.READ_CONTACTS
adb shell pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
adb shell pm grant com.google.android.setupwizard android.permission.WRITE_CONTACTS
adb shell pm grant com.google.android.setupwizard android.permission.READ_OWNER_DATA
adb shell pm grant com.google.android.setupwizard android.permission.WRITE_OWNER_DATA
NOTE IGNORE ERROR: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.READ_OWNER_DATA
AFTER SUCCESSFUL COMMANDS CHECK STATUS BAR FOR THE FINISH YOUR SETUP DEVICE AND THERE YOU GO THE SETUP SHOULD GO SMOOTH FROM HERE )
Related
Hello XDA :victory:
I just finished making a simple yet useful backup app for Android 4.0.3+ (Root needed)
It can:
Make a Nandroid backup of the following partitions: /data, /cache, /android-secure, /sd-ext, /system
Copy all user installed APK's into the sdcard
Simple, yes, but somewhat useful
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Change log:
7/26
-Option to make a full Nandroid backup
-Changed some GUI
To install:
1. Install this APK.
2. copy this file AND this file to system/bin and set permissions as 655, or run this in adb:
1. "adb push xdevilium_onandroid_data_backup system/bin"
2. "adb push xdevilium_onandroid_backup system/bin"
3. "adb shell chmod 655 system/bin/xdevilium_onandroid_data_backup"
4. "adb shell chmod 655 system/bin/xdevilium_onandroid_backup"
Credits: The creator of "onandroid" script (sorry, i forgot the username )
I see that you are using an old version of Online Nandroid. I would really appreciate if you could keep it upto date.
Btw, great attempt at an app.
ameer1234567890 said:
I see that you are using an old version of Online Nandroid. I would really appreciate if you could keep it upto date.
Btw, great attempt at an app.
Click to expand...
Click to collapse
I can't, sorry, I lost the source code and I'm working on Newgen and XDA ROM HUB now
Is it similar to the "App2zip"?
Two issue, i can download apk file but i can't download other 2 files, i receive a text web page.
Eg:-
echo "##########################################"
echo "XRH Nadroid Data Backup"
echo "* This tool backups /data partition."
echo "* It is fully compatible with nandroid."
echo "* Based on 'onandroid' By Ameer Dawood"
echo "##########################################"
echo ""
# Define constants
path="/sdcard/clockworkmod/backup"
safety=7
name="none"
tz="u"
req_power=10
sdcard_temp_mount="/mnt/sdcard4nandroid"
logfile=/data/local/tmp/onandroid.log
# Logging function
mkdir -p /data/local/tmp
[ -f $logfile ] && busybox rm $logfile
logmsg(){
message="$*"
dtime=`busybox date +%T`
echo -e "$dtime $message"
echo "$dtime $message" >>$logfile
if [ "`busybox which log`" != "" ]; then
log -p i -t onandroid "$message"
fi
}
# Process arguments
if [ $# -gt 0 ]; then
if [ $1 == "--help" ]; then
# Display usage instructions
clear
echo ""
echo "Usage: xrh_backup_script [OPTIONS] [NAME]"
echo ""
Click to expand...
Click to collapse
android addicts said:
Is it similar to the "App2zip"?
Two issue, i can download apk file but i can't download other 2 files, i receive a text web page.
Eg:-
Click to expand...
Click to collapse
Right click, save page as
I'm having trouble getting this to work. Is there anyway you can all the install steps into the app for me
Sent from my SCH-I800 using Tapatalk 2
hello guys,yesterday i flashed smoothrom 4.1 and everything was fine. Today i noticed that some root apps are telling me to allow root access through supersu. In supersu i found that all my root apps were granted.Then i downloaded Root checker from google play and it is telling me i have no root. I have already tried flashing supersu.zip from TWRP....after booting backup it is still not rooted. Any solution for this.i am willing to reflash everything except wiping my device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
more details from root cheker pro : Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 1.25 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 96260 2013-03-21 15:36 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Nexus 7 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn
problem solved
i myself don't know what i did...but i have root access again
I realize there's plenty of threads with more or less the exact same topic. But I haven't found an answer in any of them that helps my situation.
Alright here's the deal:
I'm getting the "Storage space running out"-notification. And apps are starting to FC.. My phone is a i9505 and I'm currently running Carbon. But this was a problem with CM 10.2 too.
Here's what confuses me:
Code:
[email protected]:/data # busybox df -m
Filesystem 1M-blocks Used Available Use% Mounted on
...
/dev/block/platform/msm_sdcc.1/by-name/userdata
9351 9300 50 99% /data
...
/dev/fuse 9351 9300 50 99% /mnt/shell/emulated
...
/dev/block/vold/179:33
30688 25851 4837 84% /storage/sdcard1
Those should be the interesting bits (I'm showing off my 32GB external card here as well). Right, so I'm using 99%, or 9300MB.
Now here's how I check what's taking up the space:
Code:
[email protected]:/ # du -d1 -m /data
1 /data/dontpanic
3404 /data/media
1 /data/misc
1 /data/local
252 /data/data
1 /data/app-private
176 /data/app-asec
203 /data/app-lib
939 /data/app
1 /data/property
1 /data/ssh
1 /data/radio
321 /data/dalvik-cache
1 /data/resource-cache
1 /data/lost+found
1 /data/drm
1 /data/mediadrm
1 /data/security
4 /data/system
1 /data/wpstiles
1 /data/wiper
1 /data/shared
1 /data/fota
1 /data/time
1 /data/bluetooth
1 /data/audio
1 /data/.ssh
1 /data/tombstones
1 /data/nfc
1 /data/user
6 /data/qcks
1 /data/backup
1 /data/anr
5302 /data
du sums it up for us: 5302MB on /data
DiskUsage is showing me "System data" is taking up the space, but it doesn't tell me what or where:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've checked solutions mentioned in related threads (all over the internets):
* The "/datadata" issue - I don't have this directory
* The "lost + found" - It's 1MB as you can see
* The "/data/log" issue - I don't have this directory
So what am I missing?
Well wouldn't you know. After a reboot the usage is down and df reports the same as du. I'm still confused as to what took up the space though.. I even got Java exceptions (from DiskUsage) saying the disk was full.
Below is the results from Root Checker Pro. I used Towelroot to Root this device a few weeks ago. When i opened SuperSu today I got a prompt to install the SU binary again. Here are the SS's.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I tap OK I get this:
I tap normal and get this:
And then the app closes. Trying again after a reboot produces the same results.
I know that it successfully rooted a few weeks ago and all apps that need root access are functioning fine. Xposed and other root apps are running flawlessly. Knox is unharmed at 0x0 and there is no custom recovery yet. (Wasn't sure if I wanted to void warranty yet). I was considering flashing Safestrap tonight but I don't want to proceed if there are issues. Any suggestions?
-------------
Congratulations! You have root access!
Super User Application Status:
SuperSU application - version 2.01 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 125420 2014-09-29 15:03 su
Analysis: Setuid attribute is not present BUT root user ownership is present. Root access IS correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SM-N900V - Android 4.4.2 device by Root Checker Pro version 1.3.7 from joeykrim in the Android Market - http://goo.gl/NcnHn
I usually select the twrp option and then reboot and try the install a couple times...eventually it will take.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide almost halves the battery consumption on a Samsung Galaxy Tab S3/S4 with Android 8.0.
Compared for example with a Google Pixel C, the battery on a Samsung Galaxy Tab reduces significantly faster due to some unnecessary apps from Samsung and a questionable and very comprehensive tracking of user data.
This tutorial is very careful with deactivating apps and only covers the absolutely crucial apps. Other tutorials remove significantly more apps, but this has no effect on battery consumption.
Hint: Operating the Galaxy Tab S3 under Android 8 is highly recommended as the performance is 25%-50% faster than under Android 7.
1. Install the following Google apps to later remove the sluggish and battery consuming Samsung apps:
Gmail
Contacts
Clock
Calculator
2. Disable the following packages, which consume battery unnecessarily:
Code:
adb shell su -c pm disable com.samsung.android.app.clockpack
adb shell su -c pm disable com.samsung.android.calendar
adb shell su -c pm disable com.samsung.android.contacts[I] (* If you want to use the phone dialer, then don't disable this package!)[/I]
adb shell su -c pm disable com.samsung.android.email.provider
adb shell su -c pm disable com.samsung.android.providers.context
adb shell su -c pm disable com.samsung.android.rubin.app
adb shell su -c pm disable com.samsung.android.voc
adb shell su -c pm disable com.sec.android.app.clockpackage
adb shell su -c pm disable com.sec.android.app.popupcalculator
adb shell su -c pm disable com.sec.android.app.sbrowser
adb shell su -c pm disable com.sec.spp.push
3. Optional: Remove remaining bloatware
Code:
adb shell su -c pm disable com.android.providers.partnerbookmarks
adb shell su -c pm disable com.microsoft.office.excel
adb shell su -c pm disable com.microsoft.office.onenote
adb shell su -c pm disable com.microsoft.office.powerpoint
adb shell su -c pm disable com.microsoft.office.word
adb shell su -c pm disable com.samsung.android.ststub
adb shell su -c pm disable com.samsung.android.knox.containeragent
adb shell su -c pm disable com.samsung.android.knox.containercore
adb shell su -c pm disable com.samsung.knox.securefolder
adb shell su -c pm disable com.samsung.knox.securefolder.setuppage
adb shell su -c pm disable com.sec.enterprise.knox.attestation
adb shell su -c pm disable com.sec.enterprise.knox.cloudmdm.smdms
adb shell su -c pm disable com.sec.enterprise.mdm.services.simpin
adb shell su -c pm disable com.sec.enterprise.mdm.vpn
4. Optional: Disable more unnecessary apps
Code:
adb shell su -c pm disable com.sec.android.app.kidshome
adb shell su -c pm disable com.sec.android.emergencylauncher
adb shell su -c pm disable com.sec.android.widgetapp.samsungapps
adb shell su -c pm disable com.sec.android.widgetapp.webmanual
adb shell su -c pm disable com.sec.musicstudio
If anyone has any further tips, please contact me.
Thanks, rainman. May I ask, which app you are using above?
corwin_amber said:
Thanks, rainman. May I ask, which app you are using above?
Click to expand...
Click to collapse
It's GSam Battery Monitor Pro
Can't do this with unrooted devices right? Since it uses "su -c"?
Anyway "adb shell su -c pm disable" doesn't work on my Tab S3.
Tried "pm uninstall -k --user 0 <name of package>" and it works but it uninstalls it though.
Package Disabler pro for Samsung
Hi,
Same Problem with unrooted device here. Can not disable the mentioned apps by using adb from my computer. Completely uninstalling is a bit risky I guess.
Found an app called Package Disabler Pro for Samsung instead. Works on unrooted stock devices and disables every app you want. Just tick the checkbox near to it. If you can not find the mentioned packages by name use the search function on top.
Works great, but you have to pay for it. For me it is worth that.
https://play.google.com/store/apps/details?id=com.elmklmsamsung.batteryaddon
Edit: Read on another place that Samsung AASA Service has to be disabled running oreo. Works for me.
Every app from the OP can be disabled with this command, no root necessary: $ pm disable-user --user 0 PACKAGENAME
You find more here: https://forum.xda-developers.com/galaxy-tab-s3/how-to/debloat-unbloat-tab-s3-android-8-0-0-t3906338
ItsOnlyMeAgain said:
Hi,
Same Problem with unrooted device here. Can not disable the mentioned apps by using adb from my computer. Completely uninstalling is a bit risky I guess.
Click to expand...
Click to collapse
Possibly unrelated question..
My understanding is that if you uninstall an app, that modifies the /system partition, which would then fire dm-verity on next boot.
I also am at a loss as how the app can be truly uninstalled with the /system partition read only.
So does "pm uninstall..." actually uninstall on an unrooted device?
Thanks in advance for any clarification here.
-Pie