Database Users

[APP] [4.0.3+] App Backup (Simple backup app) [update 7/26]

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

Lost root on smoothrom 4.1(urgent help needed)

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

[Q] corrupted EFS

Hello, well I ran out of battery and recharged, when turned the phone back on it has no IMEI, tried different things going from reflash the firmware, change sim card, flash radios, etc, even flashed CM and several other roms aosp roms.
At the end i went back to stock with ODIN but the device its stuck in samsung logo and if go to recovery it says failed to mount /efs (file too larger).. nvm this i falsh cf autotoot in order to be able to follow this:
ptolomeo said:
We finally fixed it. I'll post the solution in case it can help anyone else...
The S3 got stuck in the Samsung logo screen:
{
"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 entering the recovery it gave us this error "E: failed to mount /efs (Invalid argument)"
As we already know, the /efs folder contains all the personalized information of the mobile (IMEI number, carrier lock, etc). So if we like to play with ROMs, we should be aware of this detail and make several backups of this VERY IMPORTANT folder, and preferably store them out of the mobile, in the computer for example.
in case we mess up the /efs folder, we are likely to have no other solution than bringing it to the authorized Samsung dealer for repair. No one is going to lend us the EFS backup from their mobile, as doing that we would likely clone their IMEI -which is, BTW, unlegal.
So we first flashed with PC-ODIN a STOCK ROM (I9300XXDLJ4_I9300PHEDLI1_PHE). We tried different ones (one file, 4 files) and none of them solved our problem as the problem was with the /efs partition and I don't think any ROM will touch that...
After flashing the ROM we also flashed Chainfire's CF-Root (CF-Auto-Root-m0-m0xx-gti9300)
We boot up the mobile in recovery mode (Volume UP + Power + Home), we connected to the PC through ADB SHELL.
Our first surprise, trying to partition:
#mke2fs / dev/block/mmcblk0p3
sh: mke2fs: not found
It seems that mke2fs is a command provided by busybox, and it's not present in the stock ROM.I downloaded a precompiled busybox version from busybox.net and pushed it in the S3
Code:
PC> adb shell mkdir /data/busybox
PC> adb push busybox /data/busybox
PC> adb shell
$su
#cd /data/busybox
#chmod 775 busybox
#./busybox --install
once installed we could use mke2fs command properly:
Code:
# busybox mke2fs /dev/block/mmcblk0p3
busybox mke2fs /dev/block/mmcblk0p3
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
5136 inodes, 20480 blocks
1024 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193
and after that mounting the partition in the /efs folder
Code:
#busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs
busybox mount -w -t ext4 /dev/block/mmcblk0p3 /efs
With the EFS folder fixed, we ADB PUSHED the backup of ur efs folder (efs.tar), we unpackaged it (busybox tar xfv efs.tar) and moved it's content to the newly fixed /efs folder.
Reboot and ready to go:
Click to expand...
Click to collapse
but then when I try to use the tool http://forum.xda-developers.com/showthread.php?p=42407269 I type ADB SHELL it connects and the type SU and says does not exist.. if do mkdir directly it says acces denied.. so I asume that the phone is not rootes even tho I have flashed cf auto root.. so i just falsh philz recovery and flash CM or any kind of Rooted kernel and keep happening the same thing over and over..
so the thing its I DO have an efs backup but I CAN NOT restore it by any method.. would apreciate any help here to get my phone going again.. thanks in advance

If your efs backup is tar.gz format , just unpack it with winrar or 7zip , you'll get efs folder upon extraction just delete phone's efs folder contents and copy extracted efs backup folder contents to phone with root explorer and reboot.
That's it.
sent from marijuanated muffin cut into pieces by My Shining Katana

kangerX said:
If your efs backup is tar.gz format , just unpack it with winrar or 7zip , you'll get efs folder upon extraction just delete phone's efs folder contents and copy extracted efs backup folder contents to phone with root explorer and reboot.
That's it.
sent from marijuanated muffin cut into pieces by My Shining Katana
Click to expand...
Click to collapse
OK you got my attention but HOW do I "just delete phone's efs folder content and copy extracted efs backup folder content to phone " as I clearely stated that the phone WON'T boot to Android its in samsung boot loop but i can acces recovery and odin modes

I can connect the phone to the pc and DO TeamViewer IF someone is able to help me..

any help there?
Enviado desde mi GT-N7100 usando Tapatalk

msedek said:
any help there?
Enviado desde mi GT-N7100 usando Tapatalk
Click to expand...
Click to collapse
Flash philz cwm recovery.
Then via recovery go to mounts and storage and mount efs:
adb shell
cd efs
adb push file_name_here (from your extracted backup)
Click to expand...
Click to collapse
Then you have to set the required permissions file by file.
Here is the permissions of my efs folder:
-rw-rw-r-- 00000000.authtokcont
drwxrwxr-x /FactoryApp
drwxrwxr-x /bluetooth
drwxr-xr-x /carrier
drwxrwx--- /drm
-rw------- gyro_cal_data
-rw-r--r-- h2k.dat
-rw------- hw_offset
drwxrwxr-x /imei
drwxrwxr-x /log
-rw-rw---- ss_data
drwxrwxr-x /wifi
-rw-r--r-- wv.keys
-rwxrwxr-x imei/mps_code.dat
-rw-rw-r-- wifi/.mac.info
Thanks

[Q] Storage space running out - but what's using it?

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.

Xperia Z5 Lineage OS 17.1(Android 10) GAPPS issue [FIX]

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 )