Database Users

My poor G2 - In 2 pieces. Advice..?

so my lovely G2 had a personality split.. sorta. as you can see from the attached image its done for. however, the bottom part (with the battery) still may work, even though its without the screen. when i plug it into my computer though, nothing happens. but nothing happened when i plugged it in when it was not broken either, its only when i set it to the USB storage device is when the PC recognized it.
i really would like to get a bunch of **** off this phone if possible. i had a lot of stuff on the SD card (including a bunch of apps that were installed/moved on the card), but all my texts and such are on the phone.
is there a way to get that stuff of the phone, through some debugging software maybe? also, the apps that are on the sd card, how would i put them on the whatever new phone i get? they're not with the .apk extension.
thanks guys for any help

Hey sell me it or something I want that front part so bad.
Sent from my Energized Amaze 4G
Or My Sexy Nexus 7
Yes girls know about XDA
you can thank a girl on here

how did u do that? take a look at the instruction how to change the display maybe you get forward with it

xbleem said:
how did u do that? take a look at the instruction how to change the display maybe you get forward with it
Click to expand...
Click to collapse
i was thinking of swapping the display, but don't want to risk buying one and then it not working anyway due to the damage elsewhere on the phone. i think i'll just buy another g2. love the ergonomics of it. got a galaxy s3 as a replacement and can't stand it. way too huge for me and the design is awful.

Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.

gee one said:
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
Click to expand...
Click to collapse
thank you. i will fiddle with that this weekend.
what is the jtag info you're referring to?

It's a protocol from communicating wiht the chips directly- it's usually used to unbrick android devices, but I don't recall too much info for the g2, other than someone posted a pict of some of the jtag ports.
If you have a recent cwm backup, that will probably be the easiest way to recover. As a matter of fact, I did that just now. I upgraded to jellybean, but in a moment of noobness, I wiped data before backing up the two files that have to be backed up manually (mileage.db and wpa_supplicant.conf). A little command line hacking and everything is right in the world.

gee one said:
Anything on the sd card you can grab with a USB reader and a PC.
All your other goodies will be in your /data directory. If you have a recent CWM backup, you can grab the data off of there. It will be data.img and probably in a yaffs or ext3/4 format.
Otherwise, you could try booting into recovery or fastboot to see if you can get adb access, in which case, you can pull the data manually.
If it doesn't boot because there is no screen, you could try replacing/reattaching the ribbon cable to get it to boot long enough to pull data.
Lastly, I thought there was limited jtag info for the G2, so that might be a last ditch effort.
Click to expand...
Click to collapse
If you have a friend with another G2, you could probably mimic button presses in order to do a nandroid backup (then extract the /data image).
Failing that, I'm sure someone on here could give you the exact button press count to do what you need to.

the thing is guys, i'm not very good with adb. i found a few videos online on how to do a screen portion swap along with the rails. and i'm going to bid on a G2 on ebay. i'll swap the screen and rails from the one i buy to my G2. see if that works, then probably just sell the unused portion of the other G2. i will hook up my G2 to adb though tomorrow. i have to install it when i get home. anyone know the link to the adb download?

what kind of OS do you have? It's much easier in linux, if you know linux.
There might be a link to a binary, but this will get you going with adb.
https://developer.android.com/sdk/index.html
You don't need to update everything - just the SDK platform tools.
So how bad is it? What type of data are you trying to save? Most of it will probably be on the SD card. Do you have a clockwork mod backup?

[BackupTool] SM-G900P Backup Utility

Hi guys,
I created this tool so you can backup the partitions for the Sprint Galaxy S5.
This is IMPORTANT because the tools available at the moment don't backup your data properly. Trust me you don't want to corrupt your modem and then don't have a backup to restore it as they are easily corrupted when you play with network locks.
Password: ifyourhappydonate
Enjoy

Reserved

What format does this backup to and how to restore?
Sent from my SM-G900P using XDA Free mobile app

This backup to bin format.This means it's a copy of the bytes of the partitions in your phone. I did not create a restore function yet but can be added on the next version as well as support to more devices.

Only G900P ?

Yes at the moment this is the only supported phone.

josuelopezv said:
Yes at the moment this is the only supported phone.
Click to expand...
Click to collapse
Is this an automated dd process? I looked at it quickly and it appears that it is. Just curious.

josuelopezv said:
This backup to bin format.This means it's a copy of the bytes of the partitions in your phone. I did not create a restore function yet but can be added on the next version as well as support to more devices.
Click to expand...
Click to collapse
And where does it store said backups? I clicked on the backup button before i had even connected the phone and it said it backed up everything, then after connecting the phone, it did the same exact thing, yet no files found anywhere.
Thanks!

anderd said:
And where does it store said backups? I clicked on the backup button before i had even connected the phone and it said it backed up everything, then after connecting the phone, it did the same exact thing, yet no files found anywhere.
Thanks!
Click to expand...
Click to collapse
This tool is an quick tool that I created that is an automated process that uses adb to connect to the phone and create a backup and save them to the PC. This is because the available tools did not backup the correct information or are partial backups that are useless. I didn't add a verification for to see if the phone is connected but can be added later on. The files are stored in the same folder as the exe.
Requirements: Usb Debugging enabled only.

josuelopezv said:
This tool is an quick tool that I created that is an automated process that uses adb to connect to the phone and create a backup and save them to the PC. This is because the available tools did not backup the correct information or are partial backups that are useless. I didn't add a verification for to see if the phone is connected but can be added later on. The files are stored in the same folder as the exe.
Requirements: Usb Debugging enabled only.
Click to expand...
Click to collapse
Well thats odd because i have USB Debugging enabled and i dont find any files other than the ones i un-rar'd to the folder. I'll try again in the morning when im not half asleep. Thanks for the reply!

anderd said:
Well thats odd because i have USB Debugging enabled and i dont find any files other than the ones i un-rar'd to the folder. I'll try again in the morning when im not half asleep. Thanks for the reply!
Click to expand...
Click to collapse
Still same results, i see commands being processed by the phone but they're all remove commands for the BIN's its supposed to have created, from the sdcard partition. Yet i still dont find these files in the STool folder or anywhere on my phone. That and it seems to backup/dump everything so quickly its hard to believe its writing to anything unless these partitions are SUPER small. Wonder if i need to flash back to a stock rom and try from there since i recently flashed over to RDDT fo play with the WiFi calling feature. I'll flash back to stock and see if that makes a difference.
Thanks again for your work on this!

Hey
Same thing on my side, I read it but cant seem to find the file and Im on stock....???

I guys sorry for the confusion it appears that any way this is not the way to backup the data specially for the modem.
Samsung really lock this thing down and encrypted the partitions for nv ram and isolated them through hardware encrypted communicators.
i have found how to access those files i will let you know as soon as it is ready.

[Q] Backup from TWRP with USB

I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.

Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?

I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.

Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet

Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.

beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.

Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.

Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.

Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s

Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.

Nandroid Backup of 6P to new 6P with no extra storage space?

Hey guys,
I had to get a new Nexus 6P because my other one was having the background echo problem. But, anyways, how would I transfer the data from one phone to the other, so it seems like nothing changed?
I know about making a Nanroid backup, but my phone is a 64gb with only 5 gb left, so leaving that option out. I can't find a way to save the nanroid directly to the computer?

minni1986 said:
Hey guys,
I had to get a new Nexus 6P because my other one was having the background echo problem. But, anyways, how would I transfer the data from one phone to the other, so it seems like nothing changed?
I know about making a Nanroid backup, but my phone is a 64gb with only 5 gb left, so leaving that option out. I can't find a way to save the nanroid directly to the computer?
Click to expand...
Click to collapse
The only way is via a nandroid backup, you'll need to free up some space temporarily.

Heisenberg said:
The only way is via a nandroid backup, you'll need to free up some space temporarily.
Click to expand...
Click to collapse
Yeah seems like i dont have a choice but to remove some apps and such
Just out of curiosity, what exactly is the difference using Nanroid backup and Titanium backup, and which do you recommend?

minni1986 said:
Yeah seems like i dont have a choice but to remove some apps and such
Just out of curiosity, what exactly is the difference using Nanroid backup and Titanium backup, and which do you recommend?
Click to expand...
Click to collapse
Well a nandroid backup will make a snapshot of your device exactly as it is, with not only apps backed up, but all of your settings as well. Titanium will only backup your apps. I'd choose the nandroid option. Just make sure you only backup system, data, and boot (leave all other options unchecked).

Back when I was using a Nexus 5, I use a OTG cable so I could backup/restore to a 256GB USB flash drive.
Will the same setup work for a 6P?

logic88 said:
Back when I was using a Nexus 5, I use a OTG cable so I could backup/restore to a 256GB USB flash drive.
Will the same setup work for a 6P?
Click to expand...
Click to collapse
I haven't tried it personally, but it's worth a try.

Heisenberg said:
I haven't tried it personally, but it's worth a try.
Click to expand...
Click to collapse
I'll order one on amazon and see what it would do, but it seems unlikely since it would not create 2 SDcard slots in Android. Worth giving it a shot.

minni1986 said:
I'll order one on amazon and see what it would do, but it seems unlikely since it would not create 2 SDcard slots in Android. Worth giving it a shot.
Click to expand...
Click to collapse
I'm curious if it will work as well as I'm sure at some point, I won't have enough space on the 6P to run a nandroid backup.
Finding an appropriate USB-C OTG cable might be tricky too since I've heard so many bad things about out of spec USB-C cables. I tried using a USB-C adapter on my old micro USB OTG cable and it didn't work.

logic88 said:
I'm curious if it will work as well as I'm sure at some point, I won't have enough space on the 6P to run a nandroid backup.
Finding an appropriate USB-C OTG cable might be tricky too since I've heard so many bad things about out of spec USB-C cables. I tried using a USB-C adapter on my old micro USB OTG cable and it didn't work.
Click to expand...
Click to collapse
Its a pretty good idea and worth a shot.
I order 2 different cables,
a direct type c cable
http://www.amazon.com/Adapter-VicTs...&redirect=true&ref_=oh_aui_detailpage_o00_s00
and a USB 2.0 cable
http://www.amazon.com/Adapter-Samus...&redirect=true&ref_=oh_aui_detailpage_o00_s00
Also I ordered a type-c 64gb memory stick
http://www.amazon.com/Patriot-Stell...&redirect=true&ref_=oh_aui_detailpage_o00_s00
I'll keep you updated on what happens, i'll get the package wednesday

this http://www.amazon.com/Adapter-Femal... c to usb 3&qid=1462291528&ref_=sr_1_2&sr=8-2 works with my 6P

I back up to a flash drive all the time.
Slow, but it works.

Quick update:
all the wires i had listed work just fine. I prefer the 64gb usb type-c memory stick, since it was smaller and easier to use.
I had created a nanroid backup of everything and then transferred it from my old 6P to my new 6P...everything worked...kinda...the fingerprint didn't work. I did realize it until after and when i read into it, it seems its due to the fingerprint having some special ID number linked to it.
So it seems i have to start from scratch and/or use titanium to restore the apps.
also to note, i had to use an app called stick mount to write to the USB. I will probably look more into this later for a better app, but it works for now. Also to note, you have to be rooted to properly use this app.
One down side, make sure to keep your battery charged as you will not be able to charge and back up the data.

There have been more updates on another thread that i started about the issue with restoring with a nanroid.
as far as external storage, use a thumbdrive or otg cable. This thread could be closed and marked solved.

Why not just backup your whole phone directly to the PC with ADB? There are many tutorials online. Here's one.
http://www.technipages.com/how-to-backup-your-entire-android-device

floepie said:
Why not just backup your whole phone directly to the PC with ADB? There are many tutorials online. Here's one.
http://www.technipages.com/how-to-backup-your-entire-android-device
Click to expand...
Click to collapse
That is completely different to nandroid backup.
Sent from my Nexus 6P using Tapatalk

I tried the same thing albeit going from a 32 GB device to a 128 GB. Others have as well. Fingerprint reader will not work. Wiped and started over - cannot live without the fingerprint reader.

minni1986 said:
Quick update:
all the wires i had listed work just fine. I prefer the 64gb usb type-c memory stick, since it was smaller and easier to use.
Click to expand...
Click to collapse
What did you format the USB memory stick to? Did you have to use FAT32?
I had an ExFAT 256GB flash drive that wasn't recognized but a FAT32 1GB flash drive was.
Not being able to use ExFAT would be kinda weird since that means no files larger than 4GB.

Ah, the ExFAT problem is with Marshmallow's OTG support only.
I was able to backup to an ExFAT flash drive when booted into TWRP.
Edit: Though I did read elsewhere on XDA that StickMount works with ExFAT so I will have to test that out later.

Hope this might help someone else in this thread as I have done some further tests. Maybe other scenarios might get the fingerprint reader working.
Once fingerprints have been used, even deleting/disabling it does not seem to allow the restored backup to configure finger prints again. I have 2 sets of 6P. Let's say A & B.
1. Backup A with Fingerprint and restore to B
Result : Fail
Delete Locksettings
Result : Able to unlock and set pattern lock but setting fingerprint will always not be able to register new fingers, use current fingers or delete earlier registered fingers
2. Backup A without Fingerprint and restore to B
Result : Fail
Delete Locksettings
Result : Able to unlock and set pattern lock but setting fingerprint will always not be able to register new fingers at all
3. Backup A without any security of pattern lock or Fingerprint and restore to B
Result : Fail
Delete Locksettings
Result : Able to unlock and set pattern lock but setting fingerprint will always not be able to register new fingers although it says no fingers registered. Keeps saying "Unable to complete registration".
Seems like as what a few other members have encountered. all TWRP restores to a new device will result in the fingerprint reader being totally useless. Will have to do restores with Titanium Backup on a newly setup 6P till someone figures this out.

mobileman88 said:
Hope this might help someone else in this thread as I have done some further tests. Maybe other scenarios might get the fingerprint reader working.
Once fingerprints have been used, even deleting/disabling it does not seem to allow the restored backup to configure finger prints again. I have 2 sets of 6P. Let's say A & B.
1. Backup A with Fingerprint and restore to B
Result : Fail
Delete Locksettings
Result : Able to unlock and set pattern lock but setting fingerprint will always not be able to register new fingers, use current fingers or delete earlier registered fingers
2. Backup A without Fingerprint and restore to B
Result : Fail
Delete Locksettings
Result : Able to unlock and set pattern lock but setting fingerprint will always not be able to register new fingers at all
3. Backup A without any security of pattern lock or Fingerprint and restore to B
Result : Fail
Delete Locksettings
Result : Able to unlock and set pattern lock but setting fingerprint will always not be able to register new fingers although it says no fingers registered. Keeps saying "Unable to complete registration".
Seems like as what a few other members have encountered. all TWRP restores to a new device will result in the fingerprint reader being totally useless. Will have to do restores with Titanium Backup on a newly setup 6P till someone figures this out.
Click to expand...
Click to collapse
Hey Thanks for the Testing. TWRP definitely needs a setting to refuse to backup hardware device/drivers/model/serial numbers. That way the backup is just app files and settings to the point of allowing the phone backup will copy from device A to device B as a perfect mirror image without affecting device/drivers/model/serial numbers. I wonder if anyone can get in touch with the developers so we can figure something out.

how to retrieve an image out of a tablet with all the data & apps

Hello,
is there a tool to retrieve a full image out of the tablet with all the data & applications?
and another tool to flash the tablet again with this image?

Jasmin74 said:
Hello,
is there a tool to retrieve a full image out of the tablet with all the data & applications?
and another tool to flash the tablet again with this image?
Click to expand...
Click to collapse
TWRP - available here on XDA.

Yes I know it but will it do a FULL backup ? Data & Apps?
& as far as I tested , you can only restore the same tab from which you retrieved the tab. So I can't restore the image on another tablet EVEN if it's from same brand & version.

Jasmin74 said:
Yes I know it but will it do a FULL backup ? Data & Apps?
& as far as I tested , you can only restore the same tab from which you retrieved the tab. So I can't restore the image on another tablet EVEN if it's from same brand & version.
Click to expand...
Click to collapse
Yes it's apps and data ... and I never tried restoring a nandroid on another device, so no idea.

all u need to do is to change the serial number inside your twrp backup with the one you want to flash the image on and it will appear in the list after that.
let me know if you need more informations to achieve this.
in shell command type
getprop ro.serialno
it will give you the proper serial

it works well, thank you for your help
IET_DEMO said:
all u need to do is to change the serial number inside your twrp backup with the one you want to flash the image on and it will appear in the list after that.
let me know if you need more informations to achieve this.
in shell command type
getprop ro.serialno
it will give you the proper serial
Click to expand...
Click to collapse
It works well, thank you for your help

IET_DEMO said:
all u need to do is to change the serial number inside your twrp backup with the one you want to flash the image on and it will appear in the list after that.
let me know if you need more informations to achieve this.
in shell command type
getprop ro.serialno
it will give you the proper serial
Click to expand...
Click to collapse
Now it works well, thank you!