I need N900T backup file to restore

If any of you have backup file uploaded somewhere pls send me link to download it. Ty in advance

how to make a backup rom with mtk droid tools

As anybody able to backup infinix hot2 X510 rom with mtk droid tools? Because is like mtk droid tools is having problem communicating with this mtk6580 device

Backup for fingerprint unlock?

The fingerprint sensor is one reason I might update my N5 to a 5x and I was wondering what unlock methods are provided if you can't get a good fingerprint read, such as when wearing gloves (gets cold in this part of the country!).

Sent from my SM-T700 using Tapatalk

Restore new Moto X from a TWRP backup of old Moto X after unlocking bootloader.

Hey all,

Just a quick question here. I got a new replacement for my Moto X Pure that seemed to have a charging port get stuck in usb charging only.

Can I unlock the bootloader then flash TWRP and after that restore a TWRP backup I have saved from the old phone to the new one? Will that work and save me all the time of re-rooting and xposed intstalls?

I can't recall ever having an issue like this where I replaced the phone and then restored a backup from the other phone.

Thanks,
Hasherx1

moto xt1097 error backup recovery TWRP

Hello, I have the moto xt1097 2014, and when I want to backup the TWRP recovery v2.8.7.1 pulls me this error

Code:

---

E:/ Unable to create folder: /data/media/0/TWRP
(errono=13)
E:Failed to make backup folder.

---

Moto G randomly recovers itself to a "backup"

Hey, everyone!:silly:
I'm using CM 12.1 motoG 1st gen(attacked kernel) , and sometimes the phone shuts down randomly, and reboots., when it finishes the reboot, it just "erases" all the things that i've downloaded or received in a certain period of hours, something similar to doing a backup restoring, plus i lose all the WiFi passwords. I saw that this is most commom when my charger plug is somehow is misplugged, and leads the phone to a short circuit, or something.

I want to know if there's some way to stop this, or diminish the "Backup" period time, so i wont lose any data and passwords!:good:
if anyone could help, i'll be very grateful!

ta backup needed

I need to restore the original ta partition for my Xperia M2 (D2306) anybody has the backup file for me?

Crazy problem with backup and then not powering back on. V500

I have the V500 on CM12.1 unofficial. Everything was fine and then I went to do a backup in TWRP. Then I looked at the restore menu but didn't do anything. I backed up to my SD Card. Then I booted back into the system, but all that came on was the back button and the notification tray and status bar. The background was black. No home button or multitask button. So I reset it a few times. Eventually I could get into the tablet but when I clicked on a app nothing opened. I then reset it again and it kept coming on with that partial screen. I tried to boot into recovery to try and restore the backup but ADB was locked and the button combination didn't work. So I decided to flash back to stock using LG Mobile Tools. Eventually I could get into download mode but when it got close to finishing to flash the software it stopped and gave me an error. After doing some hard reboots it eventually flashed the software because it would boot into the LG screen. But it was stuck in a bootloop and I've read that in order to fix that you need to do a factory reset. So I tried to boot to recovery but when I pressed and held down volume down and power nothing would happen. Sometimes it would flash the LG logo for a split second. Eventually after a lucky try the LG logo stayed on and I could boot to recovery and do a factory reset. Then everything was back to stock. But when I turn off the tablet it won't power back on unless I plug in the tablet. Battery is fine. Regular battery life it just won't turn on when I power it down without being on the charging screen.

Provide TWRP Backup

Is there anyone who can provide me a TWRP backup of stock 5.1 lollipop latest (23.26.8) straigtfrieght bug fixed one please anyone provide.

How to have a backup of a game in non rooted android lollipop

Hi devs

As question says.

A method in which i can play a game to level x and then do a backup.

Factory reset my device and reinstall game and restore the backup

And start playing from level x from where i left.

Sent from my LG-X160 using XDA Free mobile app

Best way to backup DRM and root Lollipop 5.1.1.?

Had to upgrade my Nexus 4 to an Xperia Z1c a while ago, and that **** was eeeaaasy as hell to root.
Now, is there a step by step tutorial on how to root 5.1.1. while KEEPING the DRM / backing it up? Dont wanna mess anything up here.

how to restore whatsapp backup on another device?

hi,i bought new xperia z1.my old phone was xperia s.i want to restore my whatsapp data to z1.i don't know how to do this.i just copied whatsapp folder to my xperia z1's sd card and installed whatsapp.before i go any further i just wanna clarify something.is there anything else i need to do?

How to restore system apps uninstalled by Titanium backup

Hi, everyone,

I uninstalled some system apps by Titanium Backup and cannot restore them.

• com.android.bluetooth 4.4.2


• org.codeaurora.bluetooth 4.4.2

I didn't know system apps cannot be restored after uninstallation by Titanium Backup. Googling on the web and this forum didn't solve the issue. I need these apps to use a bluetooth keyboard.

How would you solve this problem? Thanks in advance!

[My environment]

• Model : Sony Xperia SO-04F


• Android version : 4.4.2


• Kernel version : 3.4.0-perf-g0ce556e

How can I backup my ROM? TWRP

So I just got this phone today and I want to backup my ROM with TWRP, however it will only detect OTG USB's that are 4GB's and lower which isn't enough to backup my stock ROM. Anyway to fix this?

Is there a way I can route TWRP to my PC and backup and restore that way?

[WIP] command line nandroid-like backup all variants

Ok, so I successfully rooted my H810 G4 via LER. I was impressed with being able to dump the system.img of my phone, inject root into it, then write it back to my phone. So, I thought, why can't we just back up ALL the partitions of our phones this way and if something goes wrong, those of us who do NOT have a KDZ or TOT file to flash back to original factory can just go into download mode and dd our phones back to factory!! Now I have followed this tutorial here:
http://forum.xda-developers.com/show....php?t=2450045
to learn how to dump partitions. HOWEVER, what I do NOT yet understand is why he does not use any of the bs,skip,count variables in the dd command. So I need help understanding these and I am doing more reading on it here and there. What I don't know is are these variables partition specific, or are they only PHONE specific and we can just use the same variables for each partition?
I have an ATT H810 running H81010b firmware. Here is all my partition info!

Code:

---

C:\Users\petermg\Downloads\G4>adb shell
shell@p1:/ $ cat /proc/partitions
cat /proc/partitions
major minor  #blocks  name

 253        0    721784 zram0
 179        0  30535680 mmcblk0
 179        1      88064 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3      1024 mmcblk0p3
 179        4      1024 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7        512 mmcblk0p7
 179        8      2048 mmcblk0p8
 179        9      1024 mmcblk0p9
 179      10        512 mmcblk0p10
 179      11      1024 mmcblk0p11
 179      12        512 mmcblk0p12
 179      13        512 mmcblk0p13
 179      14      2048 mmcblk0p14
 179      15        512 mmcblk0p15
 179      16        512 mmcblk0p16
 179      17        512 mmcblk0p17
 179      18        512 mmcblk0p18
 179      19        512 mmcblk0p19
 179      20        512 mmcblk0p20
 179      21      1536 mmcblk0p21
 179      22      16384 mmcblk0p22
 179      23      32768 mmcblk0p23
 179      24      1536 mmcblk0p24
 179      25      1536 mmcblk0p25
 179      26      1536 mmcblk0p26
 179      27        512 mmcblk0p27
 179      28        512 mmcblk0p28
 179      29        512 mmcblk0p29
 179      30      2048 mmcblk0p30
 179      31        512 mmcblk0p31
 259        0        512 mmcblk0p32
 259        1        512 mmcblk0p33
 259        2        512 mmcblk0p34
 259        3      2048 mmcblk0p35
 259        4      4096 mmcblk0p36
 259        5      49152 mmcblk0p37
 259        6      40960 mmcblk0p38
 259        7      40960 mmcblk0p39
 259        8      8192 mmcblk0p40
 259        9      8192 mmcblk0p41
 259      10      32768 mmcblk0p42
 259      11      8192 mmcblk0p43
 259      12      4096 mmcblk0p44
 259      13      4096 mmcblk0p45
 259      14      16384 mmcblk0p46
 259      15      40960 mmcblk0p47
 259      16      8192 mmcblk0p48
 259      17      47104 mmcblk0p49
 259      18      2048 mmcblk0p50
 259      19      10240 mmcblk0p51
 259      20      6144 mmcblk0p52
 259      21    4636672 mmcblk0p53
 259      22    1261568 mmcblk0p54
 259      23  24100864 mmcblk0p55
 259      24      12271 mmcblk0p56
 179      32      4096 mmcblk0rpmb
shell@p1:/ $


ls -al /dev/block/platform/f9824900.sdhci/by-name

shell@p1:/ $ ls -al /dev/block/platform/f9824900.sdhci/by-name
ls -al /dev/block/platform/f9824900.sdhci/by-name
lrwxrwxrwx root    root              2015-01-01 15:37 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx root    root              2015-01-01 15:37 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx root    root              2015-01-01 15:37 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx root    root              2015-01-01 15:37 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx root    root              2015-01-01 15:37 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx root    root              2015-01-01 15:37 cache -> /dev/block/mmcblk0p54
lrwxrwxrwx root    root              2015-01-01 15:37 carrier -> /dev/block/mmcblk0p47
lrwxrwxrwx root    root              2015-01-01 15:37 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx root    root              2015-01-01 15:37 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx root    root              2015-01-01 15:37 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx root    root              2015-01-01 15:37 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx root    root              2015-01-01 15:37 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx root    root              2015-01-01 15:37 eri -> /dev/block/mmcblk0p43
lrwxrwxrwx root    root              2015-01-01 15:37 factory -> /dev/block/mmcblk0p49
lrwxrwxrwx root    root              2015-01-01 15:37 felica -> /dev/block/mmcblk0p48
lrwxrwxrwx root    root              2015-01-01 15:37 fota -> /dev/block/mmcblk0p51
lrwxrwxrwx root    root              2015-01-01 15:37 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx root    root              2015-01-01 15:37 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx root    root              2015-01-01 15:37 grow -> /dev/block/mmcblk0p56
lrwxrwxrwx root    root              2015-01-01 15:37 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx root    root              2015-01-01 15:37 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root    root              2015-01-01 15:37 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx root    root              2015-01-01 15:37 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx root    root              2015-01-01 15:37 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx root    root              2015-01-01 15:37 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx root    root              2015-01-01 15:37 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root    root              2015-01-01 15:37 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx root    root              2015-01-01 15:37 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root    root              2015-01-01 15:37 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx root    root              2015-01-01 15:37 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx root    root              2015-01-01 15:37 operatorlogging -> /dev/block/mmcblk0p46
lrwxrwxrwx root    root              2015-01-01 15:37 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx root    root              2015-01-01 15:37 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root    root              2015-01-01 15:37 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx root    root              2015-01-01 15:37 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx root    root              2015-01-01 15:37 raw_resources -> /dev/block/mmcblk0p44
lrwxrwxrwx root    root              2015-01-01 15:37 raw_resourcesbak -> /dev/block/mmcblk0p45
lrwxrwxrwx root    root              2015-01-01 15:37 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx root    root              2015-01-01 15:37 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx root    root              2015-01-01 15:37 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root    root              2015-01-01 15:37 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root    root              2015-01-01 15:37 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root    root              2015-01-01 15:37 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx root    root              2015-01-01 15:37 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root    root              2015-01-01 15:37 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx root    root              2015-01-01 15:37 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx root    root              2015-01-01 15:37 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx root    root              2015-01-01 15:37 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root    root              2015-01-01 15:37 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx root    root              2015-01-01 15:37 spare3 -> /dev/block/mmcblk0p50
lrwxrwxrwx root    root              2015-01-01 15:37 spare4 -> /dev/block/mmcblk0p52
lrwxrwxrwx root    root              2015-01-01 15:37 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx root    root              2015-01-01 15:37 system -> /dev/block/mmcblk0p53
lrwxrwxrwx root    root              2015-01-01 15:37 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root    root              2015-01-01 15:37 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root    root              2015-01-01 15:37 userdata -> /dev/block/mmcblk0p55
shell@p1:/ $



Model: MMC 032G74 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start  End    Size    File system  Name              Flags
 1      16.8MB  107MB  90.2MB  fat16        modem
 2      117MB  118MB  524kB                pmic
 3      118MB  119MB  1049kB              sbl1
 4      119MB  120MB  1049kB              tz
 5      120MB  121MB  524kB                sdi
 6      121MB  121MB  524kB                hyp
 7      121MB  122MB  524kB                rpm
 8      122MB  124MB  2097kB              aboot
 9      124MB  125MB  1049kB              sbl1bak
10      125MB  125MB  524kB                pmicbak
11      125MB  126MB  1049kB              tzbak
12      126MB  127MB  524kB                hypbak
13      127MB  127MB  524kB                rpmbak
14      127MB  129MB  2097kB              abootbak
15      129MB  130MB  524kB                sdibak
16      130MB  131MB  524kB                limits
17      131MB  131MB  524kB                devinfo
18      131MB  132MB  524kB                apdp
19      132MB  132MB  524kB                msadp
20      132MB  133MB  524kB                dpo
21      133MB  134MB  1573kB              spare1
22      134MB  151MB  16.8MB              misc
23      151MB  185MB  33.6MB  ext4        persist
24      185MB  186MB  1573kB              modemst1
25      186MB  188MB  1573kB              modemst2
26      188MB  189MB  1573kB              fsg
27      189MB  190MB  524kB                fsc
28      190MB  190MB  524kB                ssd
29      190MB  191MB  524kB                keystore
30      191MB  193MB  2097kB              DDR
31      193MB  193MB  524kB                sec
32      193MB  194MB  524kB                encrypt
33      194MB  195MB  524kB                eksst
34      195MB  195MB  524kB                rct
35      195MB  197MB  2097kB              persistent
36      197MB  201MB  4194kB              spare2
37      201MB  252MB  50.3MB              laf
38      252MB  294MB  41.9MB              boot
39      294MB  336MB  41.9MB              recovery
40      336MB  344MB  8389kB  ext4        drm
41      344MB  352MB  8389kB  ext4        sns
42      352MB  386MB  33.6MB  ext4        mpt
43      386MB  394MB  8389kB              eri
44      394MB  398MB  4194kB              raw_resources
45      398MB  403MB  4194kB              raw_resourcesbak
46      403MB  419MB  16.8MB              operatorlogging
47      419MB  461MB  41.9MB              carrier
48      461MB  470MB  8389kB              felica
49      470MB  518MB  48.2MB              factory
50      518MB  520MB  2097kB              spare3
51      520MB  531MB  10.5MB              fota
52      531MB  537MB  6291kB              spare4
53      537MB  5285MB  4748MB  ext4        system
54      5285MB  6577MB  1292MB  ext4        cache
55      6577MB  31.3GB  24.7GB  ext4        userdata
56      31.3GB  31.3GB  12.6MB              grow

(parted)

---

So if you guys can chime in and help get this figured out, also I will post updates for what I learn about it. Hopefully we can get this so that we can do backups this way until we get a custom recovery for the most of us with locked bootloaders!:good:

Titanium Backup not seeing old backups

Hello everyone,

I'm hoping you can help me with an issue I'm having with Titanium Backup not being able to see old backups. I just reflashed stock de-odexed 5.0.1 using Flashfire. In Flashfire I set it to wipe 3rd party apps before flashing. The flash went fine and my phone went through the setup fine, and I chose not to restore all my app/setting from Google. All the TB backups were still on my SD card and I set the backup location in TB to the old directory on my SD card. But my problem is when I got to restore user apps in TB, it can't see any of the old backups in the TB directory on my SD card. Anyone else ever experience this? Did you find a way to fix it so TB could see all the old backups?

Thanks.

Eric

Not Able to Take Nandroid BackUp in TWRP (V2.8.7)

Hi

When i try to take backup in TWRP it says E:Unable to mount storage
Then BackUp Failed

Pls Help need to take a Backup


Thanks & Regards
Tharun Gowd :(

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 5X - Drivers, Unlock, Backup, Flash Stock

NEXUS 5X - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID 6.0.0 BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*

NOTE: There is no custom recovery/insecure kernel available yet so root isn't available. All root and custom recovery options have been disabled in the Toolkit but will be enabled and updated as soon as it is available. All other options are still enabled including installing drivers, backing up internal storage, unlocking/relocking bootloader, downloading/flashing stock firmware image directly from toolkit, pushing/pulling files to/from device, sideloading ota files via stock recovery, rebooting device to different modes and much more

The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.

FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.2 [21st Oct 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device

--------------------------------------------------------------

SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*

DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)

NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.

Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.

--------------------------------------------------------------

WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.

ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).

MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.

AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv

--------------------------------------------------------------

PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.

--------------------------------------------------------------

1. INSTALLING ADB/FASTBOOT DRIVERS

The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.

THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.

If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.

Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.

On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.

--------------------------------------------------------------

2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT

When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.

Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).

--------------------------------------------------------------

ChangeLog:
ToolKit v1.4.2 (21st Oct 2015)
+Added support for LG NEXUS 5X [BULLHEAD]
+Updated ToolkitClean.exe to update Toolkit.exe base file to latest version
+Updated Toolkit installable Apps to latest [busybox free, root checker, easy backup, efs backup]
+Toolkit will now check needed files at startup and download if needed

ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)

--------------------------------------------------------------

USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode

How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery

Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.

--------------------------------------------------------------

*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.

Nandroid backup for the G3, is it "safe" (CloudyG3 2.5, TWRP)?

Hi Guys,

I need to return my G3 for fixing the bezel crack under warranty.

Assuming that I'll get the same device back, is it safe to do a Nandroid backup with TWRP (v2.8.7.0), return the device to stock and when I'll get it back do a restore to the backup?

Can it cause a "weird" problems (I know from experience that other brands are ok with nand backup&restore)?

Thanks