[GUIDE] Full Phone Backup without Unlock or Root - Sony Xperia P, U, Sola, Go

This is a guide which will allow you to backup your phone via ADB using one simple command. Its commonly used when flashing another firmware or ROM. Keep in mind this is experimental and not exactly publicized as a feature of ICS/JB, so don't count on this as your only method of backup! Firstly you need to have ADB, if you dont have, download and install/extract from here; JDK (Java Development Kit) if you dont have that, you can download it from here and updated Android SDK Platform Tools via SDK Manager and last but not least a drivers for your phone, you can download them from the Sony Development site. OK, let's start :victory:
1. Connect your device via USB, and go to C:\adt-bundle-windows-x86\sdk\platform-tools. Hold Shift and right click. Choose open command window here.
2. Optionally, type the command 'adb devices' to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
The following text its about the adb backup command and all about it. I recommend reading it. Thanks to copkay for the further backup process.
In ADB there is a command 'adb backup' which this thread is all about. The command parameters format is:
Code:
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
The most basic command you can use* is:
Code:
adb backup -all
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
* This may not work for every setup. If you get an error such as "adb: cannot open file ./backup.ab", use:
Code:
adb backup -all -f C:\backup.ab
Or substitute the path of your choice in place of C:\.
To explain the parameters:
Code:
-f <file>
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
Code:
-apk|-noapk
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
Code:
-shared|-noshared
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Xperias I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
Code:
-all
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
Code:
-system|-nosystem
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
Code:
<packages...>
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
Click to expand...
Click to collapse
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
Code:
adb backup -apk -shared -all -f C:\backup.ab
^ It backs up all data including music, pictures, videos, APKs etc. ^
Code:
adb backup -apk -all -f C:\backup.ab
^ It backs up ONLY the APKs, system and user ones ^
4. You will see a screen like the following:
{
"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"
}
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you will get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your phone returns to the home screen.
9. To restore, with your device connected open your command prompt again, and type:
Code:
adb restore C:\backup.ab
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, Enjoy !

Could I restore my data using this method after I rooted my device (xperia P, LB)? Will I lose root if I do?
Sent from my LT22i using xda app-developers app

good post. very helpful.

didn't use adb before so maybe iam doing somethings wrong.
usb debugging on, stock ics rooted. adb devices shows my device (xpgo).
after adb backup -apk -shared -all -f C:\backup.ab console outputs : unlock device and confirme...
but there is now backup screen on my device.
any ideas what iam doing wrong ???
thanx

stavro said:
didn't use adb before so maybe iam doing somethings wrong.
usb debugging on, stock ics rooted. adb devices shows my device (xpgo).
after adb backup -apk -shared -all -f C:\backup.ab console outputs : unlock device and confirme...
but there is now backup screen on my device.
any ideas what iam doing wrong ???
thanx
Click to expand...
Click to collapse
Thats normal, you should get a new output line when finished. It takes a hour or two
Sent from my LT22i using Tapatalk 2

DavidMKD said:
Thats normal, you should get a new output line when finished. It takes a hour or two
Sent from my LT22i using Tapatalk 2
Click to expand...
Click to collapse
i mean this screenshots that you posted. i don't get to them.
i guess they should popup after entering the command in the console, right ?
in my case nothing happens on the phone.

Mis-typed link for ADB
Thanks DavidMKD for the info...
I know the thread is over a year old, but I was referred here by XDA for assistance. For the benefit of others who might arrive here for similar help... the ADK link properties show it to be ending in "htmll" (can't post full link due to forum spam rules), and clicking on it comes up with an error 404, probably due to the extra "l" in html ?
Haven't yet gone through the process, but hoping to have a working solution soon. I read stuff from cover to cover and follow instructions to the letter, so here goes....
Cheers

Related

X10 Custom ROM AOSP 2.2.1 : How to for dummies

SINCE FREE X10 IS NOW BETA, THIS HOW TO IS NO LONGER VALID
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
** No responsability for anything, you are all responsible of what you're doing !! **
** Please follow ALL these steps. Don't try to be Indiana Jones by flashing your device without all the tools needed !!! **
INSTALL
(for 1st install)
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)​
- Download FreeX10 v0.0.1 file (NOT 002 yet !!!)
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
- On x10 :
Download and install Busybox (from Market), make sure it says "Done!".
Connect your x10 in USB, mount SD card, and copy files FreeX10.zip and install on the root of your SD Card.
Enable USB debugging (Parameters > Applications > Development).
- On your computer, go in the Tools folder, open a DOS prompt (for Windows 7 : hold CAPS + right click, you'll see Open a DOS prompt) and
type :
Code:
adb shell
(this will run ADB shell... You will get a "$")
- Type :
Code:
su
(this will make you super-user, you will get a "#")
- Type :
Code:
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
(It will display "11", "1+1", or "inflating:..." ...)
- Wait, have a beer, pray for your sins for your phone not to turn into a $600 brick
- One minute after, when it shows
Code:
All done, please reboot!
, reboot ! (But you can gently quit ADB by typing
Code:
exit
twice
)
Note : regarding me, I typed "exit" to quit ADB, I turned off ADB on phone and disconnected USB. You can do, it's even safer
- Wait up to 5 minutes for the phone to boot, it is NORMAL !!!! It looks stuck on Sony Ericsson logo and/or on Free X10 logo, it's NOT stuck !!! You MUST wait !!!!
- It will finally run normal, your phone is alive and 2.2-hearted !!
You are now eligible to install v0.0.2 (as it comes as an update).
Dual Boot usage
This rom comes with a great Dual Boot, which means the 2.2.1 is installed safely apart from your original 2.1 rom. This means you can switch back anytime to stock rom. To say it simply :
- Your Android 2.1 is here, and no changes are made to it (apps, version, etc etc). It is stored as it has to be, in the internal 1Gb phone memory storage (called the "NAND").
- FreeX10 (2.2.1) is running from image files (like .ISO files) stored in your SD Card. This means the two Android are living together peacefully, without affecting (theorically) each other.
FreeX10 mainly creates a bootloader, for you to choose whether to test 2.2.1, or go back to 2.1 for your daily use.
- To run 2.2.1 : do nothing (default boot)
- To run 2.1 : press any key at boot, when it shows "Sony Ericsson".
Notes when upgrading to v0.0.2 :
- As Android is stored into image files (.IMG), upgrading will wipe out all your content (it does a fresh "install"), make backup of what you need !
- to avoid future bugs, altough you're not forced to do, do the routines to make sure Wifi, root, packages install, ... work. This is because USB debug can break, so you won't be able to use ADB to fix these bugs
- Root is strongly recommended to work, because it's cool and because the CPU performance is set to highest : stuck at 998MHz all the time, it will drain your battery like hell ! You can switch it back to original power saving plan (ondemand plan) by using (ie) SetCPU. Root required !
If your Android goes instable, does not work anymore, or you want a fresh install after lots of tests, simply drag and drop the original v0.0.2 .img files on your SD card. This will make you boot into a fully fresh install.
For all bugs, commands, etc.. Please go first to this excellent (and very easy) thread !!
Nice..
How about one on AOSP 2.1
Perceval from Hyrule said:
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
Click to expand...
Click to collapse
nice dummies HOW TO
and ohhh my god there is dummies
all comands needed
INSTALLATION
1. Download the rom package (FreeX10_alpha-release_0.0.1.tar.bz2)
2. Unpack it to the root (main folder) of your SD Card
3. Connect your phone in USB Debugging mode
4. Open ADB shell, switch to root user (SU)
5. Issue the command
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && ./data/install
6. Reboot when installation is finished
7. Enjoy
---------------------------------------------------------------------------------------------
CHANGE BOOT PRIORITY
Copy chargemon.txt file to
/system/bin
folder ON YOUR ORIGINAL 2.1 ROM, NOT FROYO!!!
---------------------------------------------------------------------------------------------
UPGRADE TO 0.0.2 VERSION
Boot into 2.1, unpack the content of FreeX10_alpha-release_0.0.2-UPDATE.tar.bz2 into
/sdcard/FreeX10
folder and reboot into updated 2.2!
NOTES:
1. SMS vibrate is disabled by default; open Messaging, press MENU button -> settings -> vibrate -> always
2. If you don't have radio (network) after 1st boot, please open ADB shell and issue this command:
killall servicemanager
3. If you don't have root access, please open ADB shell and issue this command:
chmod 4755 /system/bin/su
---------------------------------------------------------------------------------------------
hope it helps too
UPDATE TO v.0.0.2
Note : you can only update from 0.0.1 to 0.0.2. I mean you can't do a fresh install of 0.0.2, you MUST have 0.0.1 installed !
- Download v0.0.2 from main thread.
- Run your device on your regular 2.1 rom (while off, power on, and press any button when it displays Sony Ericsson logo)
- Mount the SD Card, then copy data.img and system.img from the archive into the folder /FreeX10. Replace the two .img files.
- Reboot into 2.2, have fun ^^
OmegaRED^ said:
Nice..
How about one on AOSP 2.1
Click to expand...
Click to collapse
I'll try to do one if I get time, but I need a fully working ROM as my phone is useful for my life (still waiting for 2.1 stable )
Thanks for your posts all, it will help everybody who want to try the 2.2
(as it is safe and running from SD card, very very very cool idea !)
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
root privileges do you have it?
unmount sdcard
OmegaRED^ said:
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
Click to expand...
Click to collapse
sarcasm...love it
rendeiro2005 said:
root privileges do you have it?
unmount sdcard
Click to expand...
Click to collapse
yes mate i do have root access titanium etc works fine just cant get adb shell to run
When i installed 2.2, it rebooted and when to the sony ericsson logo for almost an hour, does this mean i have to reinstall 2.1, and if so, i would i accomplish this
fastphil said:
yes mate i do have root access titanium etc works fine just cant get adb shell to run
Click to expand...
Click to collapse
and what about sdcard?
uncheck nount/unmount
rendeiro2005 said:
and what about sdcard?
uncheck nount/unmount
Click to expand...
Click to collapse
done that too
fastphil said:
done that too
Click to expand...
Click to collapse
can you post a screenshot of cmd?
ok will do
I am still having problems also...
after I type the cmd...
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
it just says:
1+1 records in
1+1 records out
520 bytes transferred in 0.003 secs...
#
so, where am I going wrong?
fyi, I am trying to install v001, not the update, and the phone is rooted, busybox is installed. Sorry, but I have tried for a while now and I finally have to just ask for help. Thanks guys.
here pic off cmd
{
"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"
}
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
Does it work when your run "adb" command only ?
It looks to me your error is because you're not in the folder where adb.exe is
It is in folder tools, if you try to run it from root directory (where is the android app with nice icon) it won't work for sure
Edit: didn't see your screenshot >> you are NOT in the correct folder !! (so Windows is searching for a registered command which does not exist, I think there's a thread somewhere on how to add it as a registered (I mean global) command)
You must download Android SDK (22mb... Lmao regarding 4gb for iOS ), extract the archive and go in the tools folder. Here is adb.exe.
when i try & run adb exe it does not open it just closes right away

[31.12.15]IMEI(EFS)BAckup Tool N 5 I Updated for systemless root I Promo for RD/C/T

IMEI (EFS) BAckup Tool Note 5
{
"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 is simple EFS backup tool. We are very well knowing about what EFS is and why it is MUST to backup on every rooted device. If you don't know then Read this.
You needs root access to use this tool otherwise app won't open..
Location of stored file :
Device storage/MyEFS
If you unable to see backup, contact me with details of your device variant
Download :
Pro Version
XDA version (free)- Attached at end of this post.
Difference between Free/Play store
-Both version makes backup in same format and no difference in backup.
-Pro version have option to Restore with single click
-Free version will save file in MyEFS and if you make next backup it will replace older one. While play store version everytime creates new folder with date ,Time and your IMEI stamp so you can keep multiple backup as well no confulsion about which backup is made when and on which device. Also it makes copy of build.prop so you can get idea you were on which ROM when backup created)
-Play store version give notification in case backup not created.
-Weekly Auto backup feature available on play store version.
-PIT creator. Play store V1.1 added option to create PIT file from existing layout
Click to expand...
Click to collapse
This tool using generic name of partition block and you can restore with simple adb shell
dd if=/path of backup files/ of=/partition block according your device
ChangeLog
1.0 - Initial release. (3644)
1.1 - Fixed for systemless root users.
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others. In latest samsung device this information store in other partition so requires to make backup of that partition too.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM on newer ROM it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Exit "Permanent Safe Mode" This condition represent with loss of IMEI + yellow text box on homescreen with device info.here is Screenshot
Here is different method to remove it.
Method1 :
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Code:
OFF
To:
Code:
ON
Reboot device.
Method2:
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Method3
Install attached safemode_exit apk as regular app. Open from drawer - Grant su permission - Reboot when asked.
e:failed to mount /efs(invalid argument) error with bootloop
This condition usually happens with using unsupported tool (usually from play store).
To recover this, needs to use adb shell
Code:
adb shell
mke2fs / dev/block/mmcblk0p[COLOR="Red"]x[/COLOR]
mount-w-t ext4 / dev/block/mmcblk0p[COLOR="red"]x[/COLOR] / efs
x means your device EFS partition number
PS : It needs CWM and busybox installed.
Reserved 3
Reserved 4
Reserved 5
Thank you
Sent from my SM-N920T using Tapatalk
Yet another useful contribution
Thanks
Nothing happens when i try to launch the app. Is that normal, or should there be a GUI? Also tried pro version.
Sent from my SM-N920T using Tapatalk
daftlush said:
Nothing happens when i try to launch the app. Is that normal, or should there be a GUI? Also tried pro version.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Are you sure you have rooted device? As said in op it won't open without root access.
Sent from my SM-N920I using xda premium
dr.ketan said:
Are you sure you have rooted device? As said in op it won't open without root access.
Sent from my SM-N920I using xda premium
Click to expand...
Click to collapse
ohh yeah. root is 100%.
Sent from my SM-N920T using Tapatalk
daftlush said:
ohh yeah. root is 100%.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Which is your device model ?
Reinstall and click on app icon and wait till it ask for supersu. Once you grant permission then only app will show ui
Sent from my SM-N920I using xda premium
dr.ketan said:
Which is your device model ?
Reinstall and click on app icon and wait till it ask for supersu. Once you grant permission then only app will show ui
Sent from my SM-N920I using xda premium
Click to expand...
Click to collapse
t-mo. rooted. su set to auto allow.
Sent from my SM-N920T using Tapatalk
Check Super su log and see it has granted su permission to app.
i have no baseband and imei unknown after updating to latest tmo firmware and installing DarthStalker. Have backup from when i first rooted phone. will purchasing your app fix you think?
do i need to downgrade to old firmware and restore?
many thanks for all your hardwork for the community,!
Try Restoring directly if doesn't work then flash same firmware on which you made backup. If any issue or doesn't work pm me.
Before doing anything make copy of backup on multiple storage.
Sent from my SM-N920G using xda premium
Thank you so much for all the help. I am now back up and running. You are awesome ,sir.!
Got it to work. How do i find out what to type in promt to restore?
Sent from my SM-N920T using Tapatalk
nice tool, but how to restore a backup ?
nmx87 said:
nice tool, but how to restore a backup ?
Click to expand...
Click to collapse
the same question
Guys it's in the OP...use Terminal Emulator with the commands in the OP. .

[TOOL] Android Job Box v3.21 [Aug 1, 2017] [Un/Lock | Bak/Res | Recovery | Optimize]

{
"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 is for Windows ONLY at the moment.
Features:
Unlock bootloader
Relock bootloader
Backup data (all or selectable sections)
Restore data (all or selectable sections)
Optimize all OGG files on device
Zipalign all APK files on device
Batch install APKs from local PC folder
Reboot device
Reboot into recovery
Reboot into bootloader
Flash recovery
Changelog:
v3.21
* Fixed a couple commands
* Fixed broken backup menu
* Cleaned up some menu spacing
* Removed some unneeded comments
Download: v3.21-FREE
Download method 2:
There is now a free version and a donate version. The donate version requires a minimum donation of $5. First, set up a FREE GitLab account. Once you have donated, send me your GitLab username, in a PM or in this thread, and I'll add you to the repo so you have access.
I will be adding features to the donate version as I get time. I have to balance work/college/family, so my time is limited. General fixes will apply to both versions.
Requirements:
GIT (Windows download)
FREE version:
Code:
git clone https://gitlab.com/ChevyCam94/Android-Job-Box-FREE.git
cd Android-Job-Box-FREE
JobBox.bat
DONATE version:
Code:
git clone https://gitlab.com/ChevyCam94/Android-Job-Box-DONATE.git
## enter your GitLab.com username/password here when prompted ##
cd Android-Job-Box-DONATE
JobBox.bat
Previous changes:
v3.20
* Updated SOX to 14.4.1
* Updated all binaries in /Data with up-to-date versions from v26.0.1 tools
* Fixed some zipalign commands not pushing back to correct device folder
* Fixed fastboot reboot command
* Fixed main menu crashing with ENTER
* Overhauled the backup/restore sections
* Separated the CAMERA and PICTURES directories in backup/restore
* Switched to TIMEOUT instead of PING (non-skippable)
v3.10 * Updated all binaries in /Data with up-to-date versions from v26-RC tools
* Fixed menu choices in REBOOT menu
* Fixed backup and restore functions
* Fixed timing issue with bootloader lock/unlock commands
* Fixed a ton of misplaced commands
* Reworked terminal output to be more visually friendly
* Made some adb push/pull functions verbose again
* Removed some unused code blocks
* Made reboot options escapable within the script
v3.00
* Updated all data binaries in /Data with up-to-date versions
* Fixed the OGG optimization process
* Fixed mounting of /system in TWRP
* Fixed a couple menu text inconsistencies
* Removed a couple unnecessary subroutines
* Reduced the size of some subroutines
* Optimized the removal of non-apks and empty folders
Installation:
1: Extract the contents of the zip file somewhere (NO spaces in the whole folder path. Need to sort that out)
2: Double-click on JobBox.bat
Installation for method 2:
1: Navigate to a folder where you want the script (NO spaces in the whole folder path)
2: Run the commands for the version you want
3: Run JobBox.bat
NOTES:
To flash recovery, the recovery image must be in "/Data" as "recovery.img"
Optimizing OGG files is done by pulling all audio from the device, into the local computer
where the are optimized, and then pushed back to the device in their original location. HOWEVER,
be aware that optimizing an audio file too many times will break it, and cause serious loss of
audio quality. I have no way to test if the files were optimized already or not, so please keep
track of that yourself.
Optimizing APK files is done by pulling all APKs from the device, into the local computer
where they are optimized, and then pushed back to the device in their original location. There
is no verbose output (by choice), or progress animation. Believe me, its still working. Just
give it time.
No part of this script may be copied,
modified, redistributed, or included
anywhere without my written consent.
Credit goes to Lexmazter for the original template I'm using to make my script. You can find his tool HERE
Credit to Chris Bagwell for SOX
Credit to Google for the adb/fastboot binaries​
Will it be able to root as well in the future?
chevycam94 said:
This tool is a work in progress.
As I add features, I'll release new
versions of the tool. This is for
Windows ONLY at the moment.​
Click to expand...
Click to collapse
Just a heads up, you need to update the unlock command to "fastboot flashing unlock" as this is the new command for the M devices - oem unlock no longer works.​
Thanks for the heads up. Question. Is that for devices that shipped with M?
Is all data wiped when performing the unlock no matter what?
Heads up - This tool does not work for some reason, just times out every time.
FAILED : (Remote : unknown command)
finished total time : ABC-XYZ
Click to expand...
Click to collapse
Its weird if you enable ADB USB debugging via developers options and allow OEM unlock and boot into bootloader it refuses to OEM UNLOCK even when using ADB terminal commands manually
Adb Devices - Lists the device
Fastboot reboot - Works
Fastboot reboot recovery - works
Weirdness - I'll Try ADB on my chromebook see if i can do it there
hutzdani said:
Heads up - This tool does not work for some reason, just times out every time.
Its weird if you enable ADB USB debugging via developers options and allow OEM unlock and boot into bootloader it refuses to OEM UNLOCK even when using ADB terminal commands manually
Adb Devices - Lists the device
Fastboot reboot - Works
Fastboot reboot recovery - works
Weirdness - I'll Try ADB on my chromebook see if i can do it there
Click to expand...
Click to collapse
use "fastboot flashing unlock" oem unlock has been depreciated on the new nexus devices.
Tung_meister said:
use "fastboot flashing unlock" oem unlock has been depreciated on the new nexus devices.
Click to expand...
Click to collapse
Yeah i can't get that to work on my ADB drivers i think i need to pull them down from google again, ill try after dinner must eat lol
I included (just in case) the 4 adb files from my current SDK, v24.4.1. I don't have my 6P yet, so I can't test it.
Also, when someone unlocks their 6P, report back here if it clobber use of the fingerprint scanner and/or Android Pay. I want to add a warning about them in the script if it does.
chevycam94 said:
Thanks for the heads up. Question. Is that for devices that shipped with M?
Click to expand...
Click to collapse
.
It might just be for the Huawei 6P, not all MM devices not certain. Since it's a Nexus device should be fastboot oem unlock not sure why Huawei changed.
Just in case, I added in an option to choose which method to use to unlock/relock the bootloader.
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
hutzdani said:
Yeah i can't get that to work on my ADB drivers i think i need to pull them down from google again, ill try after dinner must eat lol
Click to expand...
Click to collapse
make sure you go into developer options and check "oem unlocking"
eneka said:
make sure you go into developer options and check "oem unlocking"
Click to expand...
Click to collapse
All set now had to update my ADB from the SDK, fastboot flashing unlock was not supported or listed as a command until I updated the SDK
Working on a major update to the backup and restore functions. Should really help people out with backing up certain things, not necessarily the whole thing
Ok, updated to v1.20. Now the user can choose to do a backup before unlocking/relocking, without going through two different sections. Fixed the fastboot commands, and added the ability to flash custom recovery.
MAJOR update to the script. Now available in the OP.
Now, in addition to a full backup, you can also backup and restore certain files, such as your downloads, pictures, videos, music, and even Android application data (NOT the apks, just the data user storage (/Android))
So can I use this tool to back up user data from my G4 and restore to my Nexus 6p so I don't have to reconfigure every single app? Like I can do with titanium backup if rooted?
StephenMSmith said:
So can I use this tool to back up user data from my G4 and restore to my Nexus 6p so I don't have to reconfigure every single app? Like I can do with titanium backup if rooted?
Click to expand...
Click to collapse
That's the idea. Just data, not apps....yet
Is this using chainfires systemless root method? And thanks for your contribution to the 6p
Sent from my Nexus 6P using Xparent Blue Tapatalk 2

[BREVENT] A ‘No Root’ alternative to Greenify

First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Alternative To Greenify, Native Feature
ggrant3876 said:
First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
Click to expand...
Click to collapse
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
kxdaorbit said:
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
Click to expand...
Click to collapse
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
ggrant3876 said:
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
Click to expand...
Click to collapse
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
kxdaorbit said:
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
Click to expand...
Click to collapse
Yes I read a thread yesterday that said you can use Smart Switch and back it up to your sdcard. It's getting better, I started with the T-Mobile G-1 and the only way to root and even do screenshots was with adb. I learned adb and it has served me well on android, even on the S8+ to get rid of the battery icon I had to run a few commands to get SystenTuner UI to work.
Why don't you just use Samsung built in always sleeping option for apps? Works great
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have rooted, it's not problem.
And if you don't have rooted, no other alternative third-party apps can app-standby other apps or force-stop apps quickly.
I am rooted, but the app doesnt seem to see that I am rooted.
MrPhilo said:
Why don't you just use Samsung built in always sleeping option for apps? Works great
Click to expand...
Click to collapse
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
{
"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"
}
Sent from my SM-G955F using Tapatalk
BratPAQ said:
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
how do you get here ?
crayonyes said:
how do you get here ?
Click to expand...
Click to collapse
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
BratPAQ said:
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
got it, Thanks
Where is the experimental feature to start server without adb?
mrQQ said:
Where is the experimental feature to start server without adb?
Click to expand...
Click to collapse
suku_patel_22 said:
I am rooted, but the app doesnt seem to see that I am rooted.
Click to expand...
Click to collapse
]
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have Root
Just press "back" about 6 times
And then a new menu appears
There you press on "ROOT"....

Help rooting an "Obscure" phone

So I have a Infinix Note 12 pro 4g x676b. The manufacturer of this model has another model with the same name which is more popular. Now let me get to the point. I wanted to root this phone with magisk. its android 12. I tried a few tutorials for it but i realised i need twrp, but this phone model dosent have a twrp img. So i tried the method of fastboot and adb. i patched my boot.img using magisk and then try to patch it to my mobile using my pc. The adb device gets detected and i get it into fastboot. But in fastboot the device does not get recognized. I tried installing all the drivers but the manufacturer does not provide any. I got every unnofical driver installed but still it dosent detect. And also my phone does not get detected in device manager either in other devices or portable devices. What do i do now?
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
xXx yYy said:
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
that is not my question tho. My phone does not get recognised on my windows pc
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is getting recognised as Unknown device?
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
{
"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"
}
Take note that a phone's Android is rooted if SU is present in Android's filesystem.
xXx yYy said:
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
Click to expand...
Click to collapse
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is a driver related problem.
You may be able to get your work done using wireless adb, although flashing stuff wirelessly is very risky (if the connection breaks whilst the flashing is still going on).
mvikrant97 said:
It is getting recognised as Unknown device?
Click to expand...
Click to collapse
not even an unknown device just nothing is there
potatosil said:
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
Click to expand...
Click to collapse
To root a phone's Android Fastboot isn't needed as you suppose : ADB is the correct tool.
Most people instead of adb.exe what comes with Android SDK use adbLink2 app what provides a link between your Android device and your computer.
adbLink2 features:
Install Programs without Android SDK
ADB/Fastboot enabled command-line
Busybox for root and non-root
Built-in WIFI/USB remote
Manage devices via USB or IP address
Root-aware File Manager for Android devices
Install/Uninstall Apps
Connect to devices ad hoc
Manage multiple devices from one PC
Edit XML and other files on your devices
Log file viewer for adbLink2
Hyperlinked HTML Help
adbLink2 is available for Windows, macOS and Linux/ChromeOS
BTW to clarify things, you obviously don't know of:
1.
Before I define root, it's important to understand why it exists and how it works. It's because Android uses permissions ( Linux-based permissions, to be exact ) in the file structure. Every file, every folder and every partition has a set of permissions. These permissions decide who can read a file ( look at or access the contents without changing them ), write to a file ( be able to change the contents of that file, or create a new file inside a folder or partition ) and execute a file ( run the file if it's a type that can run, like an app ). This is done based on users and permissions - certain users have access, while users who don't have the right permissions are blocked from having access.
When you first set up your phone and turn it on for the first time, you are assigned a user ID. If another user logs in via Google, they are assigned a different user ID. When an app is installed on your phone, it's also assigned a user ID of its own. The system itself is a user and other processes that need to run on your phone may have their own user ID. Everything that can do anything to any files on your Android is a user.
2.
To get elevated permissions ( root access ) you place the SU binary ( SubstituteUser ) in a spot that it can run when it's called to run - that's called a PATH - e.g /data/local/tmp. If any app is in user ID's PATH it will run without telling the system exactly where it is. You also need to make sure the SU binary is in a spot that your user ID has permission to execute ( run ) files. Any other app ( Google Play has plenty of apps that need root permissions ) will also need the same access. When you use a method to root your phone, all this is sorted out by the folks who built the root method.
3.
This is where root comes in. The SU binary uses flags when it's run to tell the system what user ID you want to switch to. For example, if I run the SU binary on my Google Pixel phone like this "su Jim -c 'mount - o rw,remount -t auto /system'" I will run the mount command as the user Jim ( after supplying Jim's password ). If I run the SU binary with no flags or arguments, it switches me to the root user. Normally you would need to supply a password, but since "root" is an unused user on Android it has no password. Running the command "su" will switch you to the user root, and assign you the user ID of 0, and put you in the root group. You are now the Super User.
4.
As the Super User you can do anything to any file, folder or partition on your Android. By anything, I mean literally anything. You can remove bloatware apps and you can also remove essential system files that break your phone. You can also do things to the hardware like change the CPU frequency and ruin your phone forever.

Categories

Resources